Your message dated Sun, 11 Dec 2005 13:19:45 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Bug#161260: gdb: quit doesn't always
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 18 Sep 2002 00:44:29 +0000
>From [EMAIL PROTECTED] Tue Sep 17 19:44:29 2002
Return-path: <[EMAIL PROTECTED]>
Received: from m8-mp1.cvx2-b.bre.dial.ntli.net (cyclone) [62.253.84.8]
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 17rSwv-0000NL-00; Tue, 17 Sep 2002 19:44:23 -0500
Received: from aps100 by cyclone with local (Exim 3.36 #1 (Debian))
id 17rSwa-0002od-00
for <[EMAIL PROTECTED]>; Wed, 18 Sep 2002 01:43:52 +0100
Date: Wed, 18 Sep 2002 01:43:46 +0100
From: Andrew Suffield <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gdb: quit doesn't always
Message-ID: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4i
X-Monty-Python: No-one expects the Spanish Inquisition!
Sender: Andrew Suffield <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
Package: gdb
(gdb) q
A debugging session is active.
Do you still want to close the debugger?(y or n) y
Detaching from program:
/home/aps100/arch/dancer-1.1/testsuite/test-work/dancer-rfc1459.client/sbin/dancerd,
process 10778
ptrace: No such process.
(gdb) q
A debugging session is active.
Do you still want to close the debugger?(y or n) y
Detaching from program:
/home/aps100/arch/dancer-1.1/testsuite/test-work/dancer-rfc1459.client/sbin/dancerd,
process 10778
ptrace: No such process.
(gdb)
Etcetera. I eventually had to kill -9 it. I guess that error should be
special-cased so that gdb does actually quit when it happens.
--
.''`. ** Debian GNU/Linux ** | Andrew Suffield
: :' : http://www.debian.org/ | Dept. of Computing,
`. `' | Imperial College,
`- -><- | London, UK
---------------------------------------
Received: (at 161260-done) by bugs.debian.org; 11 Dec 2005 18:19:47 +0000
>From [EMAIL PROTECTED] Sun Dec 11 10:19:47 2005
Return-path: <[EMAIL PROTECTED]>
Received: from nevyn.them.org ([66.93.172.17] ident=Debian-exim)
by spohr.debian.org with esmtp (Exim 4.50)
id 1ElVnW-0002ut-CB
for [EMAIL PROTECTED]; Sun, 11 Dec 2005 10:19:47 -0800
Received: from drow by nevyn.them.org with local (Exim 4.54)
id 1ElVnV-0006Wr-44; Sun, 11 Dec 2005 13:19:45 -0500
Date: Sun, 11 Dec 2005 13:19:45 -0500
From: Daniel Jacobowitz <[EMAIL PROTECTED]>
To: Andrew Suffield <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
Subject: Re: Bug#161260: gdb: quit doesn't always
Message-ID: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <[EMAIL PROTECTED]>
User-Agent: Mutt/1.5.8i
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level:
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2005_01_02
Version: 6.3-1
On Wed, Sep 18, 2002 at 01:43:46AM +0100, Andrew Suffield wrote:
> Package: gdb
>
> (gdb) q
> A debugging session is active.
> Do you still want to close the debugger?(y or n) y
> Detaching from program:
> /home/aps100/arch/dancer-1.1/testsuite/test-work/dancer-rfc1459.client/sbin/dancerd,
> process 10778
> ptrace: No such process.
> (gdb) q
> A debugging session is active.
> Do you still want to close the debugger?(y or n) y
> Detaching from program:
> /home/aps100/arch/dancer-1.1/testsuite/test-work/dancer-rfc1459.client/sbin/dancerd,
> process 10778
> ptrace: No such process.
> (gdb)
>
> Etcetera. I eventually had to kill -9 it. I guess that error should be
> special-cased so that gdb does actually quit when it happens.
FYI, this was fixed by:
2003-09-12 Jeff Johnston <[EMAIL PROTECTED]>
* top.c (quit_target): New static helper function.
(quit_force): Moved code to quit_target(). Call quit_target()
via catch_errors() to catch errors during quit.
--
Daniel Jacobowitz
CodeSourcery, LLC
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
