Re: frame cache

[Wenbo Yang <wenbo.yang@simplnano.com>]

Michael Eager wrote:

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

It depends on target . If you register dwarf2 frame sniffers to gdbarch, and 
your compiler can emit proper debugging information, gdb will not call 
analyze_prologue(). At least for our target(I did the porting), it works as 
Mark Kettenis said:
"prologue analysis should only be done as a last resort, i.e. when proper 
debug information is not available. "

> I don't see where there is any test in symtab.c or infrun.c
> which tests for debug info before calling SKIP_PROLOGUE which
> calls <target>_skip_prologue.

Because if you want to use debugging information to skip prologue, you write 
the code in this function. So, test should be place here in this function.

Wenbo
-- 
Wenbo Yang

The State Key Lab. of Information Security
Graduate School of CAS, 19A Yuquan Road, Beijing, China
Homepage: http://solrex.cn

SimpLight Nanoelectronics Ltd. 6 Zhichun Road, 10th Floor, Beijing, China
Phone: +86-10-5126-6989   ---  Email: wenbo.yang@simplnano.com