Process launch view duplication

Subprojects LLDB
1

Hello,

Our slightly modified LLDB based on v6.0 with custom platform and process has a strange problem during process launch. We see the debugger view twice. After stepping over, we see it correctly - just once. Does anybody know where the problem could be?

Process, platform, thread, event logs: https://pastebin.com/3Ecns4W5

(lldb) target create “/home/davidbolvansky/Plocha/file.xexe”
Current executable set to ‘/home/davidbolvansky/Plocha/file.xexe’.
(lldb) b main
Breakpoint 1: where = file.xexe`main + 32 at bitcnt.c:76, address = 0x000001ec
(lldb) r
info: dynamic port 45999
info: Waiting for a client…
Process 1 launched: ‘/home/davidbolvansky/Plocha/file.xexe’.
Process 1 stopped

  • thread #1, stop reason = breakpoint 1.1
    frame #0: 0x000001ec file.xexe`main(argc=1, argv=0x000008c0) at bitcnt.c:76
    73 long i, j;
    74 unsigned long count;
    75
    → 76 for (i = 0; i < BENCHMARK_RUNS; i++)
    77 {
    78 count = 0;
    79 for (j = 0; j < DATA_TAB_SIZE; j++)
    Process 1 stopped
  • thread #1, stop reason = breakpoint 1.1
    frame #0: 0x000001ec file.xexe`main(argc=1, argv=0x000008c0) at bitcnt.c:76
    73 long i, j;
    74 unsigned long count;
    75
    → 76 for (i = 0; i < BENCHMARK_RUNS; i++)
    77 {
    78 count = 0;
    79 for (j = 0; j < DATA_TAB_SIZE; j++)
2

Generally, the driver will print stop info every time a stop event is forwarded from the private event queue to the public event queue. You can check the output of the event log (log enable lldb event) to see if you are indeed sending two events. If you are sending two events, you can add the -S option to the log command to see the stack trace when the events were broadcast to the public event queue and see if there's an obvious way to suppress one of them.

Jim