From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com, drow@false.org
Subject: Re: [remote/rfc] Let GDB know if a remote server originally attached to a process.
Date: Sat, 07 Mar 2009 14:20:00 -0000 [thread overview]
Message-ID: <ubpsdmn3j.fsf@gnu.org> (raw)
In-Reply-To: <200903071227.36757.pedro@codesourcery.com>
> From: Pedro Alves <pedro@codesourcery.com>
> Date: Sat, 7 Mar 2009 12:27:36 +0000
> Cc: brobecker@adacore.com,
> drow@false.org
>
> On Saturday 07 March 2009 10:29:42, Eli Zaretskii wrote:
>
> > > +@item qAttached:@var{pid}
> > > +@cindex query attached, remote request
> > > +@cindex @samp{qAttached} packet
> > > +Return if the remote target is attached to the process with the
> > > +specified process ID, instead of having created it.
> >
> > This sentence probably needs to be rephrased, but I don't understand
> > what it means, and so cannot suggest how to rephrase it. It sounds
> > like you meant to say "Return an indication of whether the remote
> > target is attached ...", but then what is the purpose of adding
> > "instead of having created it"? Could you please explain?
>
> Let me try. This is about returning an indication of how did the
> process that is now under the stub's control originaly get under
> the stub's control. Was it due to an "attach"-like operation?, or, was
> it due to a "run"-like operation? The latter was the "created it"
> version.
In that case, I suggest this text:
Return an indication of whether the remote stub attached to an
existing process or created a new process.
next prev parent reply other threads:[~2009-03-07 14:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 1:17 Pedro Alves
2009-03-04 19:18 ` Joel Brobecker
2009-03-06 21:24 ` Pedro Alves
2009-03-07 10:29 ` Eli Zaretskii
2009-03-07 12:27 ` Pedro Alves
2009-03-07 14:20 ` Eli Zaretskii [this message]
2009-03-07 14:53 ` Pedro Alves
2009-03-07 15:58 ` Eli Zaretskii
2009-03-13 16:14 ` Daniel Jacobowitz
2009-03-14 10:22 ` Pedro Alves
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=ubpsdmn3j.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=pedro@codesourcery.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