From: Dave Brolley <brolley@redhat.com>
To: sid@sources.redhat.com
Subject: --gdb and --persistent
Date: Mon, 23 Feb 2004 21:30:00 -0000 [thread overview]
Message-ID: <403A7110.4010305@redhat.com> (raw)
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
next reply other threads:[~2004-02-23 21:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-23 21:30 Dave Brolley [this message]
2004-02-25 1:22 ` Ben Elliston
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=403A7110.4010305@redhat.com \
--to=brolley@redhat.com \
--cc=sid@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).