This is the mail archive of the
mailing list for the GDB project.
Re: MI: performance of getting stack arguments
- From: Jim Ingham <jingham at apple dot com>
- To: Vladimir Prus <ghost at cs dot msu dot su>
- Cc: gdb at sources dot redhat dot com
- Date: Tue, 18 Apr 2006 09:41:53 -0700
- Subject: Re: MI: performance of getting stack arguments
- References: <email@example.com>
Do you really have a UI that shows the stack arguments for ALL the
frames on the stack? That's very unusual (and visually a bit
overwhelming, I would imagine). The usual stack display shows the
stack with just the function names. Then clicking on any given stack
will populate the arguments for that frame, fill the source window
with the source for that frame, etc... This way, you only need to
fetch the arguments for the bottom-most frame on the stack when you
stop stepping. You would only fetch the other stack arguments if the
user specifically requests them.
For most purposes, when you are stepping through a function you don't
really care what the arguments higher up on the stack are, and even
if you want to see them once you rarely need to see if they are
changing after each step. Having them always visible sounds like it
would make the UI very noisy. Fetching them without displaying them
is a waste of time, since you can fetch them one by one on demand.
On Apr 18, 2006, at 9:10 AM, Vladimir Prus wrote:
I've run into a performance problem with "-stack-list-arguments 1"
I issue the command in order to obtain stack arguments for all
I've 129 frames. Each frame has just a couple of arguments.
command execution takes 608 ms.
If this command is issued repeatedly, the time is roughly the same.
1. Any ideas why the command takes so long?
2. Any ideas what should I do to to avoid making user wait half-a-
each "step"? I can try to reload stack only when current frame id
But then, each time I enter a new function, there's still that
Incidentally, it seems that Eclipse does no show arguments in stack
all, but that does not seem the right solution.