This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [RFC] Prints the frame id when target stops
On Wed, Jan 17, 2007 at 10:59:13PM +0100, Frédéric Riss wrote:
> Have you an idea how you would like the caching to work? Do you mean not
> discarding the frame cache, or caching the returned string?
How much do we know about why it takes a long time?
For instance:
- We can speed up the psymtab lookup which currently shows up in
profiles. A coworker of mine gave me some clever ideas on how
to do this if anyone wants to try it :-)
- We can speed up prologue analyzers by judicious use of caching,
in a way that's completely reliable. DWARF2 CFI is already pretty
speedy.
If these sorts of things are enough to help...
> Also, I don't see how we could have better checks within GDB than within
> the frontend. The only reliable check is IMHO to compare frame ids after
> steps and nexts.
I suspect you can only do this in stepi, really - step/next can end up
in strange places...
--
Daniel Jacobowitz
CodeSourcery