From: Daniel Jacobowitz <drow@false.org>
To: gdb@sourceware.org
Subject: Re: Problem with breakpoint addresses
Date: Mon, 30 Oct 2006 16:44:00 -0000 [thread overview]
Message-ID: <20061030164414.GA11764@nevyn.them.org> (raw)
In-Reply-To: <4546257E.50207@st.com>
On Mon, Oct 30, 2006 at 04:17:02PM +0000, Andrew STUBBS wrote:
> Sorry it's taken me a little while to get back to this.
>
> Daniel Jacobowitz wrote:
> >Secondly, this is just our use of CORE_ADDR as a native arithmetic type
> >coming home to byte us. We knew it would someday. I think you should
> >figure out where the sign extended CORE_ADDR was created, and why.
> >I hope it was in value_as_address. This isn't a right final fix, but
> >could you see if setting gdbarch_integer_to_address to a function that
> >always uses extract_unsigned_integer helps?
>
> This fix does indeed solve the problem. Thanks.
>
> Why do you think this isn't the right final fix? I can't think of an
> example of why this wouldn't always work until SH5, but the fix need not
> affect that.
I can't remember how my logic went. Should have written more of it
down.
Some day, I think we're going to need to do as Mark and Michael
suggested; stop using CORE_ADDR so indiscriminately as a convenient
integer type. In the mean time, perhaps everywhere that doesn't
define integer_to_address should get a better default, or the fallback
case in value_as_address should be changed, so that this is fixed
equally on other platforms.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-10-30 16:44 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 [this message]
2006-10-30 16:55 ` Andrew STUBBS
2006-10-30 17:07 ` Daniel Jacobowitz
2006-10-13 18:39 ` Michael Snyder
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=20061030164414.GA11764@nevyn.them.org \
--to=drow@false.org \
--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