From: Daniel Jacobowitz <dan@debian.org>
To: Michael Uhler <uhler@mips.com>
Cc: "'Maciej W. Rozycki'" <macro@linux-mips.org>,
'Johannes Stezenbach' <js@linuxtv.org>,
linux-mips@linux-mips.org
Subject: Re: gdb vs. gdbserver with -mips3 / 32bitmode userspace
Date: Wed, 1 Feb 2006 14:24:04 -0500 [thread overview]
Message-ID: <20060201192404.GA11719@nevyn.them.org> (raw)
In-Reply-To: <005901c62754$b414dc80$bb14a8c0@MIPS.COM>
On Wed, Feb 01, 2006 at 09:26:57AM -0800, Michael Uhler wrote:
> Daniel,
>
> The O/S maybe doing something different, but the architecture has 3 bits in
> Status: KX, SX, and UX that enable access to the address space above 32
> bits. With these bits off, an attempt to access these addresses causes an
> exception. So while 32-bit apps have the full 64-bit address space, most of
> it is inaccessible to the 32-bit app.
That's not actually what I was referring to: there's at least one MIPS
implementation where the results of 32-bit arithmetic operations are
not just architecturally unpredictable but actually wrong if the upper
bits are not properly sign extended (I might be misremembering, but I
think I'm talking about the SB-1). That's the sort of thing that can
be basically impossible to track down if your debugger doesn't show
you the whole register.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-02-01 19:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-31 17:15 gdb vs. gdbserver with -mips3 / 32bitmode userspace Johannes Stezenbach
2006-01-31 17:36 ` Maciej W. Rozycki
2006-01-31 18:14 ` Johannes Stezenbach
2006-01-31 18:42 ` Thiemo Seufer
2006-01-31 19:23 ` Johannes Stezenbach
2006-02-01 19:07 ` Johannes Stezenbach
2006-02-01 19:20 ` Johannes Stezenbach
2006-02-01 16:44 ` Daniel Jacobowitz
2006-02-01 16:53 ` Maciej W. Rozycki
2006-02-01 17:26 ` Michael Uhler
2006-02-01 17:26 ` Michael Uhler
2006-02-01 19:24 ` Daniel Jacobowitz [this message]
2006-02-02 13:26 ` Ralf Baechle
2006-02-01 19:44 ` Johannes Stezenbach
2006-02-02 13:43 ` Ralf Baechle
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=20060201192404.GA11719@nevyn.them.org \
--to=dan@debian.org \
--cc=js@linuxtv.org \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
--cc=uhler@mips.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