From: Daniel Jacobowitz <drow@mvista.com>
To: Jim Blandy <jimb@zwingli.cygnus.com>
Cc: Andrew Cagney <ac131313@cygnus.com>,
Kevin Buettner <kevinb@redhat.com>,
gdb-patches@sources.redhat.com
Subject: Re: RFA: Do solib address arithmetic with appropriate truncation
Date: Wed, 06 Feb 2002 14:12:00 -0000 [thread overview]
Message-ID: <20020206171212.A14876@nevyn.them.org> (raw)
In-Reply-To: <nppu3ijtok.fsf@zwingli.cygnus.com>
On Wed, Feb 06, 2002 at 02:28:59PM -0500, Jim Blandy wrote:
>
> Andrew Cagney <ac131313@cygnus.com> writes:
> > Assuming a 32 bit MIPS section header and offset:
> >
> > 0x70000000
> > 0x20000000
> > ----------
> > 0x90000000 -> 0xffffffff90000000
>
> Okay, thanks.
>
> Now, on such a system --- 32 bit MIPS section headers and 32-bit
> pointers --- where will a value like 0xffffffff90000000 ever actually
> appear *on the target*? That is, why isn't this sign extension just a
> figment of GDB's imagination?
Just to provide an alternate wording of Andrew's answer - one of the
quirks of MIPS is that it can use a 32-bit data space, and a 32-bit ELF
format, and yet have 64-bit GPRs. Another is that those 64-bit GPRs
may be usable in 64-bit mode from user programs, and may not be - and
might be readable by the stub in 64-bit mode or not.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-02-06 22:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-02 17:29 Jim Blandy
2002-02-03 10:24 ` Andrew Cagney
2002-02-04 8:15 ` Kevin Buettner
2002-02-04 9:01 ` Andrew Cagney
2002-02-05 16:07 ` Jim Blandy
2002-02-05 16:39 ` Andrew Cagney
2002-02-06 11:27 ` Jim Blandy
2002-02-06 11:41 ` Andrew Cagney
2002-02-06 14:12 ` Daniel Jacobowitz [this message]
2002-02-03 23:09 ` Kevin Buettner
2002-02-05 15:30 ` Jim Blandy
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=20020206171212.A14876@nevyn.them.org \
--to=drow@mvista.com \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
--cc=jimb@zwingli.cygnus.com \
--cc=kevinb@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