From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <sid-return-755-listarch-sid=sources.redhat.com@sources.redhat.com>
Received: (qmail 18354 invoked by alias); 23 Feb 2004 21:30:58 -0000
Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm
Precedence: bulk
List-Subscribe: <mailto:sid-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/sid/>
List-Post: <mailto:sid@sources.redhat.com>
List-Help: <mailto:sid-help@sources.redhat.com>, <http://sources.redhat.com/lists.html#faqs>
Sender: sid-owner@sources.redhat.com
Received: (qmail 18346 invoked from network); 23 Feb 2004 21:30:57 -0000
Received: from unknown (HELO touchme.toronto.redhat.com) (216.129.200.20)
  by sources.redhat.com with SMTP; 23 Feb 2004 21:30:57 -0000
Received: from redhat.com (topaz.toronto.redhat.com [172.16.14.227])
	by touchme.toronto.redhat.com (Postfix) with ESMTP
	id C1A2080001E; Mon, 23 Feb 2004 16:30:56 -0500 (EST)
Message-ID: <403A7110.4010305@redhat.com>
Date: Mon, 23 Feb 2004 21:30:00 -0000
From: Dave Brolley <brolley@redhat.com>
Organization: Red Hat Canada, Ltd
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225
MIME-Version: 1.0
To: sid@sources.redhat.com
Subject: --gdb and --persistent
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-SW-Source: 2004-q1/txt/msg00032.txt.bz2

Hi,

Currently, specifying the --gdb option for SID also results in the 
application of the --persistent option. There is currently no way to 
remotely stop the SID process when it is persistent, other than killing 
the process.

I have a customer who would like to have control over this behaviour. 
i.e. he would like SID to die when GDB does. The best scenario would be 
if there is some GDB remote protocal packet that gets sent to the target 
when GDB terminates (as opposed to when it detaches as the program 
ends). Is there such a packet?

If not, some options for improving this are:

1) Do not apply --persistent automatically when --gdb is specified. The 
current behavior could still be achieved by specifying --persistent 
explicitely.
2) Add a --no-persistent option which could be specified to cancel the 
effect of the implied --persistent.

I prefer option 1), although it could have an effect on existing 
scripts, etc. which run sid.

Other options, ideas?

Dave