Re: Frame lost after 'leave' and before 'ret' instruction on i386?

[Aleksandar Ristovski <aristovski@qnx.com>]

Daniel Jacobowitz wrote:
> On Thu, May 22, 2008 at 10:29:41AM -0400, Aleksandar Ristovski wrote:
>> Daniel Jacobowitz wrote:
>>> When DWARF unwinding is not in use, there's the in_epilogue_p hook.
>>> Prologue analyzers could also detect epilogues using the same
>>> technique.  But this is slow and complicated.
>>>
>> Interestingly, the only mention of in_epilogue_p I found is in
>> ChangeLog-2004, but not a trace of it in the code? As if it was
>> silently removed without mentioning it in the ChangeLog.
> 
> As if one changelog writer made the same typo I did; it's
> gdbarch_in_function_epilogue_p.
> 

Ah.

So from what I can see, they all rely on symbol info (find_pc_partial_function).

Apparently I am missing something: if I were to write an "in_function_epilogue_p" for i386, why would I need the debug info? As a minimum, I want to check if we are at one of 'ret' instructions - no debug info needed.