Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Andrew Cagney <cagney@gnu.org>
Cc: Eli Zaretskii <eliz@elta.co.il>,
	roland@redhat.com, gdb@sources.redhat.com
Subject: Re: remote protocol support for TARGET_OBJECT_AUXV
Date: Wed, 25 Feb 2004 16:06:00 -0000	[thread overview]
Message-ID: <20040225160615.GA20953@nevyn.them.org> (raw)
In-Reply-To: <403CC515.4090201@gnu.org>

On Wed, Feb 25, 2004 at 10:53:57AM -0500, Andrew Cagney wrote:
> >>Date: Wed, 25 Feb 2004 09:34:16 -0500
> >>>From: Daniel Jacobowitz <drow@false.org>
> >>
> >>>>> 
> >>>>> 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.
> >
> >
> >If so, I think we should simply remove the ENN thing (and update the
> >docs accordingly).  It doesn't make sense, IMHO, to print a string
> >that has no useful meaning.
> 
> Er, no.  "Enn" as a reply packet is a fundamental part of the protocol 
> and can't be removed.  Whats lacking is the formal specification of its 
> contents.  For the moment I'd leave that part of roland's doco as is.

Yeah, I agree.  Eli, it does have a useful meaning: it means that an
error occured.  It just neglects to tell us _what_ :)

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2004-02-25 16:06 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
2004-02-25 15:17                   ` Eli Zaretskii
2004-02-25 15:54                     ` Andrew Cagney
2004-02-25 16:06                       ` Daniel Jacobowitz [this message]
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=20040225160615.GA20953@nevyn.them.org \
    --to=drow@false.org \
    --cc=cagney@gnu.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