This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/14725] Ctrl-C cygwin/mingw32
- From: "palves at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Wed, 02 Jan 2013 19:18:35 +0000
- Subject: [Bug gdb/14725] Ctrl-C cygwin/mingw32
- Auto-submitted: auto-generated
- References: <bug-14725-4717@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14725
Pedro Alves <palves at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |palves at redhat dot com
--- Comment #2 from Pedro Alves <palves at redhat dot com> 2013-01-02 19:18:35 UTC ---
Cygwin strace is unreadable to me.
In any case, "set debug remote 1" should show GDB sending a vCont;t packet in
response to ctrl-c. That starts out by SIGINT being handled in GDB in
handle_remote_sigint, and that setting things up for the event loop to break
and call async_remote_interrupt -> target_stop -> ... -> remote_stop_ns.
If that isn't working on Cygwin hosts, and vCont;t isn't being sent, someone
motivated will need to debug GDB and figure out why not. It was, last I tried
(years ago).
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.