From: "Nathan J. Williams" <nathanw@wasabisystems.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Eli Zaretskii <eliz@elta.co.il>,
cagney@gnu.org, roland@redhat.com, gdb@sources.redhat.com
Subject: Re: remote protocol support for TARGET_OBJECT_AUXV
Date: Thu, 26 Feb 2004 16:57:00 -0000 [thread overview]
Message-ID: <mtu8yip4w3o.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <20040226145726.GA13921@nevyn.them.org>
Daniel Jacobowitz <drow@false.org> writes:
> But GDB doesn't interpret the error code. I just skimmed remote.c; in
> some places it checks for starts-with-E; in some it checks for 'E' and
> length 3; in some it checks for 'E' and length 3 and digits; in some it
> checks for 'E' and length 3 and hex digits. The last is, I think,
> correct.
I noticed this in some recent work. My approach to fixing it was to
make remote.c in GDB only check for 'E..' (not hex digits) and to make
gdbserver return E## (hex digits), for best compatibility between
gdb and gdbservers of differing vintage.
- Nathan
next prev parent reply other threads:[~2004-02-26 16:57 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
2004-02-26 6:14 ` Eli Zaretskii
2004-02-26 14:57 ` Daniel Jacobowitz
2004-02-26 16:57 ` Nathan J. Williams [this message]
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=mtu8yip4w3o.fsf@contents-vnder-pressvre.mit.edu \
--to=nathanw@wasabisystems.com \
--cc=cagney@gnu.org \
--cc=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