This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [mi] -stack-list-arguments --simple-values
- From: Niko Sams <niko dot sams at gmail dot com>
- To: Vladimir Prus <vladimir at codesourcery dot com>
- Cc: Nick Roberts <nickrob at snap dot net dot nz>, gdb-patches at sources dot redhat dot com
- Date: Wed, 1 Jul 2009 19:44:53 +0200
- Subject: Re: [mi] -stack-list-arguments --simple-values
- References: <200906301339.30711.vladimir@codesourcery.com> <19019.24800.902658.94531@totara.tehura.co.nz> <200907012134.49196.vladimir@codesourcery.com>
On Wed, Jul 1, 2009 at 19:34, Vladimir Prus<vladimir@codesourcery.com> wrote:
> On Wednesday 01 July 2009 Nick Roberts wrote:
>
>> ?> This patch makes -stack-list-arguments --simple-values work.
>> ?> It looks like --simple-values (and friends) were accepted for
>> ?> -stack-list-locals, but not for -stack-list-arguments. While
>> ?> the utility of such human friendly spelling is unclear, for
>> ?> a machine interface, it's even more confusing having 1/2
>> ?> of relevant commands accept it.
>>
>> It's not immediately clear from the manual that SHOW-VALUES from
>> -stack-list-arguments and PRINT-VALUES from -stack-list-locals are related.
>> -stack-list-arguments takes three arguments while -stack-list-locals only
>> takes -one. ?I think it would be nice to have one command,
>> -stack-list-locals-and-args say, that lists both the locals and the arguments
>> of the current frame:
>
> It would be nice indeed. However, I have not entirely designed how a frontend
> should actually work with locals and arguments, so I did not do anything
> like that -- just fixed obvious inconsistency between existing commands.
>
Isn't every arg a local? Why would an IDE want to display arguments
and locals differently?
In KDevelop I added the arguments to the locals.
-stack-list-locals-and-args would be perfect.
Niko