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

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


--- Comment #11 from Tom Tromey <tromey at sourceware dot org> ---
One thing I notice is that the spurious stop is always a "breakpoint"
stop in some other thread, one that is ostensibly suspended:

infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=1, current thread
[Thread 5924.0x2360] at 0x4015d6
gdb: windows_resume (pid=5924, tid=0x2360, step=1, sig=0);
ContinueDebugEvent (cpid=5924, ctid=0x2360, DBG_CONTINUE);
infrun: prepare_to_wait
gdb: kernel event for pid=5924 tid=0x33a8 code=EXCEPTION_DEBUG_EVENT)
gdb: Target exception EXCEPTION_BREAKPOINT at 0x4015d6
get_windows_debug_event - unexpected stop in 0x33a8 (expecting 0x2360)

I am thinking it might be ok to simply ignore such events.

I'm a little troubled by all this because I don't truly understand
how this stop could happen, even in theory.

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

More information about the Gdb-prs mailing list