[Bug gdb/22992] GDB and Microsoft Windows thread pool

tromey at sourceware dot org sourceware-bugzilla@sourceware.org
Thu Oct 3 14:16:00 GMT 2019


--- Comment #10 from Tom Tromey <tromey at sourceware dot org> ---
I resurrected the idea from comment #7.  I realized it would
probably work fine, because we can always continue whatever
event we just processed; and then the queue of deferred stops
could be handled in windows-nat.c via synthetic stops and resumes.

This at least avoids the crash but it also causes a spurious stop:

Thread 2 received signal SIGTRAP, Trace/breakpoint trap.
[Switching to Thread 11276.0x3244]
0x004015dd in (anonymous namespace)::Callback (context=0xe8) at sample.cxx:22
22        Sleep(100);  /* Do a "work". */

You are receiving this mail because:
You are on the CC list for the bug.

More information about the Gdb-prs mailing list