From: Andreas Schwab <schwab@suse.de>
To: gdb-patches@sourceware.org
Subject: Re: Signed vs. unsigned adresses in solib-svr4
Date: Tue, 27 Mar 2007 20:20:00 -0000 [thread overview]
Message-ID: <je4po630c8.fsf@sykes.suse.de> (raw)
In-Reply-To: <20070327192144.GK28164@caradoc.them.org> (Daniel Jacobowitz's message of "Tue, 27 Mar 2007 15:21:44 -0400")
Daniel Jacobowitz <drow@false.org> writes:
> On Tue, Mar 27, 2007 at 09:16:28PM +0200, Andreas Schwab wrote:
>> All but two places in solib-svr4.c assume unsigned target addresses. This
>> patch fixes these two occurences of extract_signed_integer to make things
>> consistent.
>>
>> Andreas.
>>
>> 2007-03-27 Andreas Schwab <schwab@suse.de>
>>
>> * solib-svr4.c (LM_ADDR_FROM_LINK_MAP): Use
>> extract_unsigned_integer instead of extract_signed_integer.
>> (LM_DYNAMIC_FROM_LINK_MAP): Likewise.
>
> I'd rather not unless this fixes a real problem
If your CORE_ADDR is 64bit, but the target is 32bit you get an address
that does not exist on the target.
> - since I know that the assumption is wrong for MIPS. Isn't there an
> extract_address or something like that which would be suitable?
There is extract_typed_address, but I don't know how to construct the
struct type that it needs.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, MaxfeldstraÃe 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-03-27 20:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-27 19:16 Andreas Schwab
2007-03-27 19:21 ` Daniel Jacobowitz
2007-03-27 20:20 ` Andreas Schwab [this message]
2007-03-27 20:36 ` Daniel Jacobowitz
2007-03-29 11:38 ` Andreas Schwab
2007-03-29 17:56 ` Daniel Jacobowitz
2007-04-10 6:57 ` Kevin Buettner
2007-03-31 9:10 ` Mark Kettenis
2007-05-09 17:55 ` Ulrich Weigand
2007-05-09 18:38 ` Andreas Schwab
2007-05-09 19:46 ` Ulrich Weigand
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=je4po630c8.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=gdb-patches@sourceware.org \
/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