From: Andrew Cagney <ac131313@cygnus.com>
To: twall@oculustech.com
Cc: gdb@sources.redhat.com
Subject: Re: packing/unpacking 4-octet longs
Date: Wed, 05 Dec 2001 10:49:00 -0000 [thread overview]
Message-ID: <3C0E6C4B.7040102@cygnus.com> (raw)
In-Reply-To: <3C0E6556.A5F9D5D6@oculustech.com>
> For the most part, I'm leaving lengths as octet lengths and adjusting them to target
> lengths if necessary at the last possible instant. My remote server/stub will answer
> 1-octet requests with the LS octet of the character addressed, though this is not a
> recommended request, nor are 1-octet write requests.
I think doing this would be a bad move. GDB shouldn't lie about how the
target represents its data types.
Best example of this I can think of is with the MIPS. GDB tried to lie
and pretend that the MIPS didn't sign extended addresses.
enjoy,
Andrew
prev parent reply other threads:[~2001-12-05 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-04 5:44 Timothy Wall
2001-12-05 8:26 ` Andrew Cagney
2001-12-05 8:46 ` Richard Earnshaw
2001-12-05 10:11 ` Lars Brinkhoff
2001-12-05 10:42 ` Andrew Cagney
2001-12-06 2:03 ` Richard Earnshaw
2001-12-05 9:31 ` Timothy Wall
2001-12-05 10:03 ` Andrew Cagney
2001-12-05 10:20 ` Timothy Wall
2001-12-05 10:49 ` Andrew Cagney [this message]
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=3C0E6C4B.7040102@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=twall@oculustech.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