This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA] remote.c: adjust Z packet addr using BREAKPOINT_FROM_PC
- To: Nick Duffek <nsd at redhat dot com>
- Subject: Re: [RFA] remote.c: adjust Z packet addr using BREAKPOINT_FROM_PC
- From: David Smith <dsmith at redhat dot com>
- Date: Tue, 09 Jan 2001 14:10:59 -0600
- CC: jtc at redback dot com, gdb-patches at sources dot redhat dot com
- Organization: Red Hat, Inc.
- References: <5mn1d0wnz4.fsf@jtc.redback.com> <200101091950.f09Jobr01677@rtl.cygnus.com>
I'm not exactly sure what you are trying to do here, but Kevin Buettner
posted a patch (that never got committed) that added a new architecture
feature that explicitly adjusted a breakpoint address (if necessary).
You might look at it for ideas if nothing else. The nice thing about it
is that the address "swizzling" is very explicit. Here's a link:
<http://sources.redhat.com/ml/gdb-patches/2000-06/msg00257.html>
I hope this helps.
Nick Duffek wrote:
>
> On 9-Jan-2001, J . T . Conklin wrote:
>
> >Yes, if address swizzling is necessary, I think it should be done before
> >the vector functions are called.
>
> I'll check into that.
>
> >A gdb for a given arch may support several targets. I'm still somewhat
> >concerned that address swizzling for one target may not be appropriate
> >for another. I'm probably just being paranoid.
>
> I'm a bit paranoid about prepending BREAKPOINT_FROM_PC to
> target_insert_breakpoint, but it does seem like the right approach. I'll
> bet that only a few archs use BREAKPOINT_FROM_PC to change the address, so
> it may be possible to be reasonably sure that no breakage would result.
>
> Patch withdrawn,
>
> Nick
--
David Smith
dsmith@redhat.com
Red Hat, Inc.
http://www.redhat.com
256.704.9222 (direct)
256.837.3839 (fax)