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 Fri, Jan 19, 2007 at 03:27:44PM +0100, Denis PILAT wrote:
> As there is no consensus to modify the -stack-list-frames to perform
> cache in a safe way, putting the frame_id (like discussed before) in the
> MI output allows the front end to make a compromise that isn't possible
> in GDB, and for some cases, the front end will be able to not get the
> stack list frame at all.
I understand that front end authors may want to make compromises that
we, the GDB developers, don't (in order to improve performance).
However, I don't want to provide an interface that looks simple
but carries these kinds of pitfalls if I can avoid it.
Maybe you can use Nick's MI timings patch, or a system profiler like
oprofile / vtune, to get some better idea of where time is being spent.
If we can make things fast enough, we should.
--
Daniel Jacobowitz
CodeSourcery