[Bug gdb/14725] New: Ctrl-C cygwin/mingw32

[Bug gdb/14725] New: Ctrl-C cygwin/mingw32

[jan.smets@alcatel-lucent.com]

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.

[Bug gdb/14725] Ctrl-C cygwin/mingw32

[jojelino at gmail dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=14725

gee <jojelino at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jojelino at gmail dot com

--- Comment #1 from gee <jojelino at gmail dot com> 2012-10-25 20:32:30 UTC ---
Seems related to 14685

-- 
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.

[Bug gdb/14725] Ctrl-C cygwin/mingw32

[palves at redhat dot com]

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.

[Bug gdb/14725] Ctrl-C cygwin/mingw32

[jan.smets@alcatel-lucent.com]

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

Jan Smets <jan.smets@alcatel-lucent.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P2                          |P3
           Severity|normal                      |enhancement

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