This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/775: gdb 5.2 on solaris 5.8 doesn't handle Ctrl-Z (SIGTSTP) well
- From: rrh at cray dot com
- To: gdb-gnats at sources dot redhat dot com
- Date: 30 Sep 2002 23:18:40 -0000
- Subject: gdb/775: gdb 5.2 on solaris 5.8 doesn't handle Ctrl-Z (SIGTSTP) well
- Reply-to: rrh at cray dot com
>Number: 775
>Category: gdb
>Synopsis: gdb 5.2 on solaris 5.8 doesn't handle Ctrl-Z (SIGTSTP) well
>Confidential: no
>Severity: serious
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon Sep 30 16:28:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator: rrh@cray.com
>Release: 5.2
>Organization:
>Environment:
solaris 5.8
>Description:
Running gdb 5.2 on solaris 5.8 does not seem to handle Ctrl-Z
SIGTSTP well. If I start up the debugee, type Ctrl-Z,
I get the message
^Z
Program received signal SIGTSTP, Stopped (user).
0xfeb1b144 in _read () from /usr/lib/libc.so.1
I then tell the debugger "continue", and I get
Continuing.
And then all subsequent attempts to regain control
of the inferior debuggee fail, either with Ctrl-C
(SIGINT) or Ctrl-Z. I have to go to another window, and
hunt up the inferior's pid, and use 'kill' to kill it
explicitly.
Gdb 4.17 on 5.7 does not have this behaviour.
gdb 5.2 on linux 2.4.9-31sm doesn't have this behaviour,
and seems to do the right thing.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="stop.cc"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="stop.cc"
I2luY2x1ZGUgPHN0ZGxpYi5oPgojaW5jbHVkZSA8c3RkaW8uaD4KaW50IG1haW4odm9pZCkKewog
IGNoYXIgYnVmW0JVRlNJWl07CiAgRklMRSAqZnAgPSA6OmZvcGVuKCIvZGV2L3R0eSIsICJyIik7
CiAgOjpmZ2V0cyhidWYsIEJVRlNJWiwgZnApOwogIDo6ZmNsb3NlKGZwKTsKICBleGl0ICgwKTsK
fQo=