From: Paul Koning <pkoning@equallogic.com>
To: vinod.pandarinathan@gmail.com
Cc: gdb@sourceware.org
Subject: Re: MIPS 64 bit addressing query
Date: Mon, 06 Aug 2007 18:37:00 -0000 [thread overview]
Message-ID: <18103.27059.549214.117236@pkoning.equallogic.com> (raw)
In-Reply-To: <dd9cdd980708061124v5bd79829j7956366e9ca051ba@mail.gmail.com>
>>>>> "Vinod" == Vinod pandarinathan <vinod.pandarinathan@gmail.com> writes:
Vinod> Hi, Thanks for the quick reply. I upgraded the debugger to
Vinod> gdb6.6 but still seeing the same problem. I searched the
Vinod> newsgroup and found a related thread
Vinod> http://www.ecos.sourceware.org/ml/gdb/2006-10/msg00088.html
Vinod> I checked mips-tdep.c where the function
Vinod> set_gdbarch_integer_to_address uses mips_integer_to_address
Vinod> which sign extends the 32 bit value. From the above thread it
Vinod> is suggested to use unsigned integer extension. However I am
Vinod> still trying to find where the zero extended
Vinod> address[bpt->address] is coming from.
The ecos thread is for a different architecture, the SH. I don't know
about that one, but the MIPS rule is entirely clear -- 32-bit
addresses are sign extended, NOT zero extended, to make a 64-bit
address. So if you're seeing problems because of a zero-extended
address, the fix is to track down where that comes from and make it
sign-extend instead.
paul
next prev parent reply other threads:[~2007-08-06 18:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-06 0:57 Vinod pandarinathan
2007-08-06 1:20 ` David Daney
2007-08-06 1:51 ` Daniel Jacobowitz
2007-08-06 18:24 ` Vinod pandarinathan
2007-08-06 18:36 ` Daniel Jacobowitz
2007-08-06 18:37 ` Paul Koning [this message]
2007-08-14 20:20 ` Vinod pandarinathan
2007-08-14 20:32 ` Daniel Jacobowitz
2007-08-14 21:52 ` Vinod pandarinathan
2007-08-14 21:59 ` Daniel Jacobowitz
2007-08-14 22:38 ` Vinod pandarinathan
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=18103.27059.549214.117236@pkoning.equallogic.com \
--to=pkoning@equallogic.com \
--cc=gdb@sourceware.org \
--cc=vinod.pandarinathan@gmail.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