This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/1482: gdb hit by SIGTSTP?
- From: ossi at kde dot org
- To: gdb-gnats at sources dot redhat dot com
- Date: 11 Dec 2003 22:23:14 -0000
- Subject: gdb/1482: gdb hit by SIGTSTP?
- Reply-to: ossi at kde dot org
>Number: 1482
>Category: gdb
>Synopsis: gdb hit by SIGTSTP?
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Thu Dec 11 22:28:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: ossi@kde.org
>Release: 6.0-debian
>Organization:
>Environment:
pc-i386-linux
running from bash
>Description:
right after gdb startup, probably when it expects user input the first time, the same happens as if ctrl-z was pressed. i can reproduce this only when attaching gdb to a kdm (either master or subdaemon) process that is running in the background on the same tty.
>How-To-Repeat:
$ kdm -nodaemon &
$ gdb kdm $!
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: