This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug remote/17028] GDB+GDBserver hangs on Windows waiting for stop event since target-async on by default


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

Pedro Alves <palves at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |palves at redhat dot com

--- Comment #1 from Pedro Alves <palves at redhat dot com> ---
> Not sure why the event does not show up on the GDB side.
> though, and why target-async makes any difference.

I haven't tried debugging this myself, but I'm clueless atm too.

I'd suspect some gdb_select issue, but seems we block
in gdb_select too on !target-async, within
do_ser_base_readchar.

I'd add some debug output to mingw-hdep.c:gdb_select,
right after the WaitForMultipleObjects, to check whether
something odd is doing on, like actually waking up from
WaitForMultipleObjects once, but then not doing anything
with the result, and then blocking again (forever).

I was also wondering whether it'd be easy to make gdb_select
call the real select, to try to isolate/identify the
problem.  Note: I think ctrl-c would stop working properly.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]