From: Daniel Jacobowitz <drow@false.org>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Richard Henderson <rth@redhat.com>, gdb-patches@sources.redhat.com
Subject: Re: Question: Checking register value in buffer
Date: Thu, 19 May 2005 05:37:00 -0000 [thread overview]
Message-ID: <20050519033339.GA31674@nevyn.them.org> (raw)
In-Reply-To: <20050519032332.GZ12565@adacore.com>
On Thu, May 19, 2005 at 01:23:32PM +1000, Joel Brobecker wrote:
> Isn't this assument that LONGEST is exactly 64 bits? I think
> extract_signed_integer expands the value held in the given buffer
> to fit the size of LONGEST. Here is the implementation:
If you're confusing yourself with sign extension, use ULONGEST instead.
But this isn't the only thing that would break in GDB with 128-bit
types. You really don't need to be this paranoid.
--
Daniel Jacobowitz
CodeSourcery, LLC
next prev parent reply other threads:[~2005-05-19 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-19 2:49 Joel Brobecker
2005-05-19 3:03 ` Richard Henderson
2005-05-19 3:07 ` Joel Brobecker
2005-05-19 3:23 ` Richard Henderson
2005-05-19 3:33 ` Joel Brobecker
2005-05-19 4:52 ` Richard Henderson
2005-05-19 5:37 ` Daniel Jacobowitz [this message]
2005-05-19 3:26 ` Daniel Jacobowitz
2005-05-19 16:41 ` 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=20050519033339.GA31674@nevyn.them.org \
--to=drow@false.org \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sources.redhat.com \
--cc=rth@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