[Bug threads/18127] threads spawned by infcall end up stuck in "running" state

["eliz at gnu dot org" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=18127

Eli Zaretskii <eliz at gnu dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |eliz at gnu dot org

--- Comment #4 from Eli Zaretskii <eliz at gnu dot org> ---
On MS-Windows during native MinGW debugging, this issue, when it happens, makes
the debugging session unusable.  MinGW native debugging doesn't support async
execution, and therefore there's no command to stop the threads that GDB
considers "running", nor help GDB re-synchronize its notion of thread states
with the actual situation (which of course is that the threads are all
suspended by the OS).

Unlike in the examples brought here from Unix and GNU systems, I see this on
Windows when I call functions from the inferior.  Those functions don't start
any threads; the threads that trigger the problem are started by Windows for
reasons unknown to me.  And because in Windows native debugging the set_running
function is called with minus_one_ptid, it marks all the threads as running.

This isan acute problem that needs to be solved at least for the above
configuration.

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