This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Re: frame cache
Mark Kettenis wrote:
Date: Tue, 24 Jul 2007 10:35:59 -0700
From: Michael Eager <eager@eagercon.com>
When I put debugging code in <target>_analyze_prologue(), I see
that it is called over and over while executing a "next" command.
All those bits going back and forth over the serial line to the
target.
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().
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.
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.
--
Michael Eager eager@eagercon.com
1960 Park Blvd., Palo Alto, CA 94306 650-325-8077