From: Elena Zannoni <ezannoni@localhost.redhat.com>
To: "Graeme Peterson" <gp@qnx.com>
Cc: gdb@sources.redhat.com
Subject: Re: GDB MI command "-stack-list-arguments"
Date: Tue, 05 Feb 2002 16:08:00 -0000 [thread overview]
Message-ID: <15456.29667.783415.289334@localhost.redhat.com> (raw)
In-Reply-To: <200202052233.RAA3387432@node128.ott.qnx.com>
Graeme Peterson writes:
> Hi, all.
>
> I am using GDB-5.0 in MI mode. According to documentation, the
> "stack-list-arguments 1" command is supposed to display a list of
> the arguments for all frames. But it also displays all locals for
> all frames if the current frame has an argument (non-void).
>
> I don't know if it is correct or not but this is very convenient.
>
> Could someone please verify what the correct behavior should be for
> "stack-list-arguments"? Should it return the local variables at all?
> If so, should it be returning them regardless of whether or not the
> current function had non-void parameters?
>
> To see the problem debug this:
>
> #include <stdio.h>
>
> int main( int argc, char* argv[] )
> {
> int k = 0;
> return(0);
> }
>
> Then replace "int main( int argc, char* argv[] )" by "int main( void )" and
> try again.
>
> Thanks.
> Graeme Peterson.
Silly bug.
Try this, let me know if it fixes it.
Elena
Index: mi-cmd-stack.c
===================================================================
RCS file: /cvs/uberbaum/gdb/mi/mi-cmd-stack.c,v
retrieving revision 1.9
diff -u -p -r1.9 mi-cmd-stack.c
--- mi-cmd-stack.c 2002/01/17 22:15:18 1.9
+++ mi-cmd-stack.c 2002/02/06 00:06:19
@@ -279,6 +279,7 @@ list_args_or_locals (int locals, int val
ui_out_field_stream (uiout, "value", stb);
ui_out_tuple_end (uiout);
}
+ print_me = 0;
}
}
if (BLOCK_FUNCTION (block))
prev parent reply other threads:[~2002-02-06 0:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-05 14:32 Graeme Peterson
2002-02-05 15:30 ` Andrew Cagney
2002-02-05 16:08 ` Elena Zannoni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=15456.29667.783415.289334@localhost.redhat.com \
--to=ezannoni@localhost.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=gp@qnx.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox