This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: MI: performance of getting stack arguments

From: Vladimir Prus <ghost at cs dot msu dot su>
To: Robert Dewar <dewar at adacore dot com>
Cc: Jim Ingham <jingham at apple dot com>, gdb at sources dot redhat dot com
Date: Wed, 19 Apr 2006 10:10:40 +0400
Subject: Re: MI: performance of getting stack arguments
References: <e2331r$cbr$1@sea.gmane.org> <EFF204DE-4C25-4F2A-A622-8605B2996BC9@apple.com> <44455B87.2020800@adacore.com>

On Wednesday 19 April 2006 01:35, Robert Dewar wrote:

> > Also, in a GUI much more stuff is visible at once, so if each element is
> > too complex then the overall result is noisy and hard to use. Visual
> > Studio used by default to show a whole bunch of junk in the stack window
> > (pc, args, etc.) and way back when I used it I found it really hard to
> > look at for just this reason.  According to the 2005 Online docs, you
> > can turn all the other info off and display just the function name if
> > you want...
>
> Seems reasonable to have a much more streamlined call stack visible all
> the time, and a special command to decorate it with parameter values.

Good idea! I'll think about it.

Thanks,
Volodya

References:
- MI: performance of getting stack arguments
  - From: Vladimir Prus
- Re: MI: performance of getting stack arguments
  - From: Jim Ingham
- Re: MI: performance of getting stack arguments
  - From: Robert Dewar

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]