From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org, Eli Zaretskii <eliz@gnu.org>
Cc: 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:53:00 -0000 [thread overview]
Message-ID: <200903071453.38031.pedro@codesourcery.com> (raw)
In-Reply-To: <ubpsdmn3j.fsf@gnu.org>
On Saturday 07 March 2009 14:20:00, Eli Zaretskii wrote:
> 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.
Sounds very good, thank you. Here's how it looks now:
@item qAttached:@var{pid}
@cindex query attached, remote request
@cindex @samp{qAttached} packet
Return an indication of whether the remote server attached to an
existing process or created a new process. When the multiprocess
protocol extensions are supported (@pxref{multiprocess extensions}),
@var{pid} is an integer in hexadecimal format identifying the target
process. Otherwise, @value{GDBN} will omit the @var{pid} field and
the query packet will be simplified as @samp{qAttached}.
This query is used, for example, to know whether the remote process
should be detached or killed when a @value{GDBN} session is ended with
the @code{quit} command.
Reply:
@table @samp
@item 1
The remote server attached to an existing process.
@item 0
The remote server created a new process.
@item E @var{NN}
A badly formed request or an error was encountered.
@end table
--
Pedro Alves
next prev parent reply other threads:[~2009-03-07 14:53 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
2009-03-07 14:53 ` Pedro Alves [this message]
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=200903071453.38031.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=drow@false.org \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
/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