Re: frame cache

[Paul Koning <pkoning@equallogic.com>]

>>>>> "Michael" == Michael Eager <eager@eagercon.com> writes:

 Michael> Mark Kettenis wrote:
 >>  If that's the case, there's something wrong; prologue analysis
 >> should only be done as a last resort, i.e. when proper debug
 >> information is not available.
 >> 
 >> Your effort might be better spent on determining why proper debug
 >> info is not present instead of optimizing
 >> <target>_analyze_prologue().

 Michael> Perhaps so, I don't see where other targets check for debug
 Michael> info before calling analyze_prologue().  For example, on
 Michael> i386, i386_analyze_prologue() is called each and every time
 Michael> that i386_skip_prologue() is called.

I've run into other cases, with assembly language code in kernels.  It
may be that this could be cured by throwing in more magic assembly
language pseudo-ops.  Then again, I have a modified GDB that usees
prologue analysis to handle not just function calls, but also
interrupts and exceptions; this is quite handy in RTOS work.

	   paul