[Bug tdep/34195] Windows tests report "No unwaited-for children left."
tromey at sourceware dot org via Gdb-prs <[email protected]>
| Newsgroups | gmane.comp.gdb.bugs.discuss |
|---|---|
| Message-ID | <[email protected]/bugzilla/> |
https://sourceware.org/bugzilla/show_bug.cgi?id=34195 --- Comment #8 from Tom Tromey <tromey at sourceware dot org> --- (In reply to Tom Tromey from comment #7) > Anyway maybe one possible fix is to delay the final thread-exit event, > looping until we see a process-exit event, then handling both. What I tried is ignoring the EXIT_THREAD_DEBUG_EVENT for the final thread, reasoning that the subsequent EXIT_PROCESS_DEBUG_EVENT would take care of this automatically. This did not work -- it did remove the message, but now there are just test case timeouts like: (gdb) run ls Starting program: C:/Users/itmgr/sandbox/x86_64-windows64/gdb_version-head_test/tmp/test/gdb-TS-ct8fds28/K509-012__path_cmd/my_which.exe ls C:/Users/itmgr/sandbox/x86_64-windows64/gdb_version-head_test/tmp/test/gdb-TS-ct8fds28/K509-012__path_cmd/./mybin\ls.exe TIMEOUT:K509-012__path_cmd:run ls (timeout) Maybe we're back to this theory now: > I wonder if gdb could somehow be leaving the inferior in a state > that prevents the exit event. -- You are receiving this mail because: You are on the CC list for the bug.