This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
[Bug gdb/14725] New: Ctrl-C cygwin/mingw32
- From: "jan dot smets at alcatel-lucent dot com" <sourceware-bugzilla at sourceware dot org>
- To: gdb-prs at sourceware dot org
- Date: Mon, 15 Oct 2012 15:32:52 +0000
- Subject: [Bug gdb/14725] New: Ctrl-C cygwin/mingw32
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=14725
Bug #: 14725
Summary: Ctrl-C cygwin/mingw32
Product: gdb
Version: 7.5
Status: NEW
Severity: normal
Priority: P2
Component: gdb
AssignedTo: unassigned@sourceware.org
ReportedBy: jan.smets@alcatel-lucent.com
Classification: Unclassified
Created attachment 6689
--> http://sourceware.org/bugzilla/attachment.cgi?id=6689
strace
(gdb) set target-async on
(gdb) set pagination off
(gdb) set non-stop on
(gdb) set may-insert-fast-tracepoints off
(gdb) set may-insert-tracepoints off
(gdb) set displaced-stepping off
(gdb) set gnutarget a.out-i386
(gdb) target extended-remote 1.2.3.4:2159
Remote debugging using 1.2.3.4:2159
(gdb)
(gdb)
(gdb) attach 559480756
Attaching to process 559480756
[New Thread 559480756.559480756]
0x07c4e2a6 in ?? ()
(gdb) c
Continuing.
<ctrl-c> => nothing happens
<window-resize> => thread is stopped.
[Thread 559480756.559480756] #1 stopped.
A Ctrl-C or (ctrl-break) at this point should suspend the thread again. The
ctrl-c is not handled correctly by GDB.
In cygwin 1.7 the Ctrl-C is handled correctly after a *window*resize*.
See attached strace done on cygwin 1.7.
(output taken after the 'continue' has been issued. There are two parts: 1 part
is output after ctrl-c , part two is what happened after the window resize.)
--
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.