[Lldb-commits] [PATCH] D61611: [JITLoaderGDB] Set eTypeJIT for objects read from JIT descriptors
Pavel Labath via Phabricator via lldb-commits
lldb-commits at lists.llvm.org
Mon May 13 02:25:35 PDT 2019
labath added a comment.
It looks like this test is flaky:
The failure messages I've seen are all the same and seem to indicate that the "breakpoint locations added" and "process stopped" messages come out of order. This seems plausible since the two messages are reported through different channels, and I was able to reproduce this failure locally by adding a sleep(1) to Debugger::HandleBreakpointEvent.
Given that the behavior of asynchronous breakpoint location messages is not the puprose of this test, what would you say to just deleting the "# CHECK: 1 location added to breakpoint 1" line from the test?
CHANGES SINCE LAST ACTION
More information about the lldb-commits