From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org
Subject: Re: [rfc] Multiple process support in gdbserver
Date: Sat, 08 Dec 2007 18:14:00 -0000 [thread overview]
Message-ID: <20071208152935.GA4888@caradoc.them.org> (raw)
In-Reply-To: <umyslxvkb.fsf@gnu.org>
On Sat, Dec 08, 2007 at 01:41:40PM +0200, Eli Zaretskii wrote:
> > -was compiled with the correct sysroot using @code{--with-system-root}).
> > +was compiled with the correct sysroot using @code{--with-sysroot}).
>
> Does this mean the previous wording was just plain wrong, or are you
> changing the option's spelling?
It was just wrong.
> @ref does not produce a "see", so the above is wrong. Why did you
> replace @xref in the first place, it looks allright here (except that
> you need a comma after the right brace)?
Just trying to fix the info build; I'll add the comma instead.
> > +* The GDB remote stub, gdbserver, now supports run and attach in
> > +extended-remote mode.
>
> Is "extended-remote mode" a known term? If not, we should probably
> explain it, or else replace it with a more plain-language description
> of it.
I think it is a sufficiently known term; it corresponds to "target
extended-remote", which is documented.
Thanks for the comments! I will update the patch (next week).
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-12-08 15:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 10:54 Daniel Jacobowitz
2007-12-08 15:29 ` Eli Zaretskii
2007-12-08 18:14 ` Daniel Jacobowitz [this message]
2007-12-10 15:34 ` Daniel Jacobowitz
2008-01-24 1:50 ` Pedro Alves
2008-01-30 0:55 ` Daniel Jacobowitz
2008-01-30 5:55 ` Eli Zaretskii
2008-01-30 13:18 ` Daniel Jacobowitz
2008-02-14 21:09 ` --multi support for Windows targets (Re: [rfc] Multiple process support in gdbserver) Pedro Alves
2008-02-14 21:15 ` Daniel Jacobowitz
2008-02-14 22:43 ` 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=20071208152935.GA4888@caradoc.them.org \
--to=drow@false.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