From: Daniel Jacobowitz <drow@false.org>
To: Eli Zaretskii <eliz@elta.co.il>
Cc: Roland McGrath <roland@redhat.com>, gdb@sources.redhat.com
Subject: Re: remote protocol support for TARGET_OBJECT_AUXV
Date: Wed, 25 Feb 2004 14:34:00 -0000 [thread overview]
Message-ID: <20040225143415.GA18298@nevyn.them.org> (raw)
In-Reply-To: <u4qtfg152.fsf@elta.co.il>
On Wed, Feb 25, 2004 at 07:48:42AM +0200, Eli Zaretskii wrote:
> > Date: Tue, 24 Feb 2004 15:21:29 -0800
> > From: Roland McGrath <roland@redhat.com>
> >
> > > I suggest using @var{nn} (lower-case) instead of @var{NN}, since that
> > > should look better in the printed manual. Also, please explain in
> > > the text what does @var{nn} stand for; I assume it's a number that
> > > tells what kind of error happened, but I think the manual shouldn't
> > > leave that to reader's guesses.
> >
> > I copied this part of the documentation, and protocol behavior, from the
> > other existing protocol requests. As far as I can tell, they are all
> > underspecified. What gdbserver seems to do is actually write "ENN" (two
> > literal 'N's). So go figure. I'd be happy to change my additions to
> > reference a standard explanation of what error packets really look like.
>
> If gdbserver prints a literal "ENN", then @var is wrong.
>
> Does anybody know what's the story here, why ENN is printed and what
> it should be? Is this perhaps a bug?
It predates my work with gdbserver. My guess is that someone saw ENN
in the manual, realized that GDB didn't parse the error numbers to do
anything useful, and decided not to bother coming up with some.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2004-02-25 14:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <401E5DC0.9020904@gnu.org>
2004-02-04 23:58 ` Roland McGrath
2004-02-05 6:34 ` Eli Zaretskii
2004-02-05 15:54 ` Andrew Cagney
2004-02-06 2:49 ` Roland McGrath
2004-02-06 17:02 ` Andrew Cagney
2004-02-12 2:12 ` Roland McGrath
2004-02-12 6:26 ` Eli Zaretskii
2004-02-24 23:21 ` Roland McGrath
2004-02-25 5:47 ` Eli Zaretskii
2004-02-25 14:34 ` Daniel Jacobowitz [this message]
2004-02-25 15:17 ` Eli Zaretskii
2004-02-25 15:54 ` Andrew Cagney
2004-02-25 16:06 ` Daniel Jacobowitz
2004-02-26 6:14 ` Eli Zaretskii
2004-02-26 14:57 ` Daniel Jacobowitz
2004-02-26 16:57 ` Nathan J. Williams
2004-02-26 18:56 ` Eli Zaretskii
2004-02-12 16:42 ` Andrew Cagney
2004-02-24 23:29 ` Roland McGrath
2004-02-25 5:49 ` Eli Zaretskii
2004-02-25 16:06 ` 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=20040225143415.GA18298@nevyn.them.org \
--to=drow@false.org \
--cc=eliz@elta.co.il \
--cc=gdb@sources.redhat.com \
--cc=roland@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