From: fche@redhat.com (Frank Ch. Eigler)
To: Andrew Cagney <ac131313@cygnus.com>
Cc: Jim Blandy <jimb@cygnus.com>, GDB Discussion <gdb@sourceware.cygnus.com>
Subject: Re: [remote] Make registers network byteordered?
Date: Wed, 06 Dec 2000 03:51:00 -0000 [thread overview]
Message-ID: <o566kx22eo.fsf@touchme.toronto.redhat.com> (raw)
In-Reply-To: <3A2D84F3.48F372E@cygnus.com>
cagney wrote:
: [...]
: > What's the point? Simply that registers don't have an endianness?
:
: Several motivations:
: [...]
: o I've had it with trying to read
: what are endian independant values
: backwards.
Certainly a laudable goal. What would be the corresponding syntax for
the `g' and `p'/`P' packets? Is there any intended support for
mismatching register sizes (e.g., 4-byte vs sign-extended 8-byte MIPS
pointers)?
- FChE
From qqi@world.std.com Wed Dec 06 05:24:00 2000
From: Quality Quorum <qqi@world.std.com>
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Andrew Cagney <ac131313@cygnus.com>, GDB Discussion <gdb@sourceware.cygnus.com>
Subject: Re: [remote] Make registers network byteordered?
Date: Wed, 06 Dec 2000 05:24:00 -0000
Message-id: <Pine.SGI.4.21.0012060823030.23073-100000@world.std.com>
References: <o566kytwbv.fsf@toenail.toronto.redhat.com>
X-SW-Source: 2000-12/msg00031.html
Content-length: 623
On 5 Dec 2000, Frank Ch. Eigler wrote:
> Andrew Cagney <ac131313@cygnus.com> writes:
>
> : [..]
> : At present the target sends back registers in target byte order format
> : vis:
> : T0525:c4060280ffffffff;1d:c0ffff81ffffffff;
> : I'd like to think about a [tweak] to this part of the protocol so that the
> : format:
> : T0525=ffffffff80020664;1d=ffffffff81ffffc0;
> : is accepted. [...]
>
> How are gdb and the target supposed to pick the right scheme? Do you
> imagine some sort of prior negotiation?
Gdb knows what target it is working with. Can you debug unknown target ?
>
> - FChE
>
Thanks,
Aleksey
next prev parent reply other threads:[~2000-12-06 3:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3A2C4305.6D9E53B3@cygnus.com>
2000-12-05 13:03 ` Frank Ch. Eigler
2000-12-05 14:34 ` Jim Blandy
[not found] ` <3A2D84F3.48F372E@cygnus.com>
2000-12-06 3:51 ` Frank Ch. Eigler [this message]
2000-12-07 12:53 ` J.T. Conklin
[not found] <3A2ED523.70DCA415@cygnus.com>
2001-03-21 15:59 ` Todd Whitesel
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=o566kx22eo.fsf@touchme.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=jimb@cygnus.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