From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Andrew STUBBS <andrew.stubbs@st.com>
Cc: GDB List <gdb@sourceware.org>
Subject: Re: Problem with breakpoint addresses
Date: Fri, 13 Oct 2006 18:39:00 -0000 [thread overview]
Message-ID: <1160764729.14535.242.camel@localhost.localdomain> (raw)
In-Reply-To: <452F4C03.2010608@st.com>
On Fri, 2006-10-13 at 09:19 +0100, Andrew STUBBS wrote:
> Michael Snyder wrote:
> > What's the size of $r1, and what's the size of an address?
> > By converting $r1 to an address, you're applying an implied cast.
> > If that doesn't give the expected result (eg. because $r1 is signed),
> > then you need to use an explicit cast.
>
> Registers are 32 bit, addresses are 32 bit. It's just something in GDB
> that uses 64 bit. It might be because sh-elf also supports sh64.
>
> In any case, it is successfully setting the breakpoint and then failing
> to recognise it when it is hit. That isn't the behaviour I would like.
> If it totally failed to set it then giving the cast might be fair
> enough, if the user thought addresses were 64 bit.
Hmmm. Well, gdb's internal representation of a target address is
a typedef COREADDR, and usually it equates to a long long (64 bits).
Seems like, if we know that for a given architecture, an actual
target address is only 32 bits, we should always make sure to
save only 32 bits into a COREADDR.
Maybe its time we made COREADDR into a first class object, with
accessor methods. I know, I know, we can only pretend to do it in
C, but we already do treat a number of things like objects.
next prev parent reply other threads:[~2006-10-13 18:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 17:54 Andrew STUBBS
2006-10-12 19:50 ` Michael Snyder
2006-10-13 8:29 ` Andrew STUBBS
2006-10-13 13:19 ` Daniel Jacobowitz
2006-10-30 16:18 ` Andrew STUBBS
2006-10-30 16:44 ` Daniel Jacobowitz
2006-10-30 16:55 ` Andrew STUBBS
2006-10-30 17:07 ` Daniel Jacobowitz
2006-10-13 18:39 ` Michael Snyder [this message]
2006-10-15 20:00 ` Mark Kettenis
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=1160764729.14535.242.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=andrew.stubbs@st.com \
--cc=gdb@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