From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: RFA: "disconnect" command
Date: Tue, 17 Jun 2003 14:59:00 -0000 [thread overview]
Message-ID: <3EEF2CCF.7020708@redhat.com> (raw)
In-Reply-To: <20030614042642.GA28231@nevyn.them.org>
> This patch got tabled shortly before 5.3, due to bad timing on my part.
> Now here we are coming up on 6.0 and my timing's no better... this is
> the first of several old patches that I would like to see included in
> 6.0, assuming I get the time to revisit them all.
>
> Refresher on this one: the patch adds a "disconnect" commad, and
> implements it for remote targets. "disconnect" leaves the target
> stopped, while "detach" usually resumes it. Useful with kgdb,
> gdbserver, et cetera.
>
> I've included the gdbserver portion of the patch this time, too.
>
> There was a consensus on this patch the last time I posted it, but it's
> been so long that I'd like a thumbs-up from another maintainer first.
> I've corrected the doc problems; Andrew, there's still no MI testcase,
> because I could not figure out a reasonable way to write one without
> leaving a dangling process around. Re-attaching to it to kill it
> properly, from within the testsuite, ranges from hard to really hard.
>
> Thoughts? OK?
The code, yea. Just check that part in.
The doco, though, does not belong in ``Implementing a remote stub'' :-(
(the existing doco is scrambled).
Can you please insert at the start of that chapter a new section called:
@section Connecting to a remote target
and then, from ``Using the gdbserver program'' and ``Using the
gdbserv.nlm program'', replace ``On the GDB host machine'' with an @xfef
to ``Connecting to a remote target''. And move 7. on from
``Implementing a remote stub'' to the new section.
Andrew
next prev parent reply other threads:[~2003-06-17 14:59 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-14 4:26 Daniel Jacobowitz
2003-06-14 8:42 ` Eli Zaretskii
2003-06-16 13:31 ` Paul Koning
2003-06-16 13:41 ` Daniel Jacobowitz
2003-06-16 14:01 ` Paul Koning
2003-06-16 14:38 ` Daniel Jacobowitz
2003-06-16 15:05 ` Andrew Cagney
2003-06-16 23:47 ` Michael Snyder
2003-06-17 1:06 ` Daniel Jacobowitz
2003-06-17 14:29 ` Andrew Cagney
2003-06-16 23:46 ` Michael Snyder
2003-06-17 14:59 ` Andrew Cagney [this message]
2003-06-17 22:00 ` Daniel Jacobowitz
2003-06-17 22:27 ` Eli Zaretskii
2003-06-19 1:32 ` Daniel Jacobowitz
2003-06-18 14:22 ` Andrew Cagney
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=3EEF2CCF.7020708@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-patches@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