This is the mail archive of the
mailing list for the GDB project.
Re: MI: performance of getting stack arguments
- From: Eli Zaretskii <eliz at gnu dot org>
- To: Vladimir Prus <ghost at cs dot msu dot su>
- Cc: gdb at sources dot redhat dot com
- Date: Wed, 19 Apr 2006 10:30:06 +0300
- Subject: Re: MI: performance of getting stack arguments
- References: <firstname.lastname@example.org>
- Reply-to: Eli Zaretskii <eliz at gnu dot org>
> From: Vladimir Prus <email@example.com>
> Date: Tue, 18 Apr 2006 20:10:34 +0400
> I've run into a performance problem with "-stack-list-arguments 1" command.
> I issue the command in order to obtain stack arguments for all frames, and
> I've 129 frames. Each frame has just a couple of arguments. However, the
> command execution takes 608 ms.
That's an awful lot, I think. When I debug Emacs, there are sometimes
many _thousands_ of frames on the call stack (during GC, for example).
> If this command is issued repeatedly, the time is roughly the same.
> 1. Any ideas why the command takes so long?
GDB has a facility to profile itself (see "maint set profile").
Perhaps you could use that to find out where is the time sink.