This is the mail archive of the
mailing list for the GDB project.
Re:  What if EXTRA_FRAME_INFO wasn't required
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: Joel Brobecker <brobecker at gnat dot com>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 08 Apr 2003 18:07:54 -0400
- Subject: Re:  What if EXTRA_FRAME_INFO wasn't required
- References: <3E84BFD5.firstname.lastname@example.org> <20030328213935.GZ924@gnat.com> <3E878942.email@example.com> <20030331223213.GF916@gnat.com>
Will try it out. I also identified a few macros that were not converted
yet, but all of them should be easy to do, except one (FIX_CALL_DUMMY)
which I understand should be replaced in the relatively near future.
I need to find an excuse for doing it. Something as perverted as
modifying the d10v to use generic dummy frames that are on the stack
should do the trick :-)
I'm guessing that the entire dummy mess can be replaced with a single
with a default implementation looking something like:
BREAKPOINT_FROM_PC(addr, len, bytes);
write_memory (addr, len, bytes);
Can I commit your patch if it turns out to be working, or would you
prefer to do it?
I've committed the bulk of it. Suggest giving multi-arch partial a
wirl. Oh, I thought I glimpsed some ->frame or ->pc references in some
of the HP code :-(