From: David Daney <ddaney@avtrex.com>
To: Vinod pandarinathan <vinod.pandarinathan@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: MIPS 64 bit addressing query
Date: Mon, 06 Aug 2007 01:20:00 -0000 [thread overview]
Message-ID: <46B676EB.5010205@avtrex.com> (raw)
In-Reply-To: <dd9cdd980708051757h45629ce8jb8235609aa96cbd@mail.gmail.com>
Vinod pandarinathan wrote:
> Hi Experts,
>
>
> I found that gdb6.4.1 is sign extending the
> PC before comparing it to the breakpoint address[bpt->address].
>
> Sign extension happens in mips-tdep.c
>
> /* MIPS believes that the PC has a sign extended value. Perhaps the
> all registers should be sign extended for simplicity? */
>
> static CORE_ADDR
> mips_read_pc (ptid_t ptid)
> {
> return read_signed_register_pid (mips_regnum (current_gdbarch)->pc, ptid);
> }
> The target suspends at the breakpoint, but the debugger is not able to
> identify the associated breakpoint as [unsigned value is compared to a
> 64 bit sign extended value].
>
> We are using MIPS 3 ISA and since breakpoint is set at an address
> where the 32nd bit is set to 1 the 64 bit sign extended values does
> not compare with the unsigned
> break point address.
>
> Can you please explain how we can fix the problem? Should I sign
> extend the break point address too ?
>
I am running gdb-6.6 on mips64-linux (All of n32, n64 and o32 ABIs) with
no apparent problems.
Perhaps you should upgrade.
David Daney
next prev parent reply other threads:[~2007-08-06 1:20 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 [this message]
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
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=46B676EB.5010205@avtrex.com \
--to=ddaney@avtrex.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