This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/8: Ctrl-C problem with cygwin/NT host
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/8: Ctrl-C problem with cygwin/NT host
- From: Fabrice_Gautier at sdesigns dot com
- Date: 15 Nov 2000 23:07:59 -0000
- Reply-To: Fabrice_Gautier at sdesigns dot com
>Number: 8
>Category: gdb
>Synopsis: Ctrl-C problem with cygwin/NT host
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Wed Nov 15 15:18:00 PST 2000
>Closed-Date:
>Last-Modified:
>Originator: Fabrice Gautier
>Release: 5.0
>Organization:
>Environment:
Host: win NT 4 + cygwin 1.4 dll
Target: Native or remote i386-pc
>Description:
On a native target, with a simple "while(1);" program gdb crash when interrupting with ctrl-C a second time.
When setting a breakpoint in the while(1) loop, gdb does no crash withthe 2nd ctrl-C if the breakpoint was caught after the first.
On a remote target, the second ctrl-C will not crash gdb but it will not be caught.If a O packet is received from the target or a breakpoint is caught then i'm ablle to "ctrl-C" again.
The probelm also appears with the insgight GUI but in a slightly different way.
For more details see the list archives:
http://sources.redhat.com/ml/gdb/2000-11/msg00080.html
>How-To-Repeat:
Nobody reported a similar problem yet. But I can repeat the situation with 100% success.
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: