From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] Add options to skip unavailable locals
Date: Mon, 26 Aug 2013 16:40:00 -0000 [thread overview]
Message-ID: <521B84EE.70805@redhat.com> (raw)
In-Reply-To: <1377402123-3740-3-git-send-email-yao@codesourcery.com>
Looks good to me. A few tiny-tiny suggestions below:
> * NEWS: Mention the new option "--skip-unavailable" to MI
> commands '-stack-list-locals' '-stack-list-arguments' and
^
Missing comma.
> '-stack-list-variables'.
> Errors are printed as if they would be the parameter value. Use
> - zeroed ARG iff it should not be printed according to VALUES. */
> + zeroed ARG iff it should not be printed according to VALUES. If
> + SKIP_UNAVAILABLE is true, print ARG if it is available. */
"is true, only print ARG"
>
> static void
> list_arg_or_local (const struct frame_arg *arg, enum what_to_list what,
> - enum print_values values)
> + enum print_values values, int skip_unavailable)
> {
> /* Print a list of the objects for the frame FI in a certain form,
> which is determined by VALUES. The objects can be locals,
> - arguments or both, which is determined by WHAT. */
> + arguments or both, which is determined by WHAT. If SKIP_UNAVAILABLE
> + is true, print the arguments or local variables whose values are
> + available. */
"is true, only print the"
>
> static void
> list_args_or_locals (enum what_to_list what, enum print_values values,
> - struct frame_info *fi)
> + struct frame_info *fi, int skip_unavailable)
> {
> struct block *block;
--
Pedro Alves
next prev parent reply other threads:[~2013-08-26 16:40 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 1:48 [PATCH 0/2] New option --skip-unavailable to -stack-list-XXX commands Yao Qi
2013-07-03 1:48 ` [PATCH 1/2] Use mi_getopt in mi_cmd_stack_list_locals and mi_cmd_stack_list_variables Yao Qi
2013-07-29 18:17 ` Pedro Alves
2013-07-31 7:01 ` Yao Qi
2013-07-31 12:23 ` Pedro Alves
2013-08-01 6:45 ` Yao Qi
2013-07-03 1:48 ` [PATCH 2/2] Add options to skip unavailable locals Yao Qi
2013-07-03 4:14 ` asmwarrior
2013-07-03 5:21 ` Yao Qi
2013-07-03 19:22 ` Eli Zaretskii
2013-07-22 1:38 ` Yao Qi
2013-08-01 12:33 ` Pedro Alves
2013-08-01 13:59 ` Yao Qi
2013-08-01 14:47 ` Pedro Alves
2013-08-25 3:43 ` [PATCH 0/2 v2] " Yao Qi
2013-08-25 3:43 ` [PATCH 2/2] " Yao Qi
2013-08-26 16:40 ` Pedro Alves [this message]
2013-08-27 5:22 ` Yao Qi
2013-08-25 3:43 ` [PATCH 1/2] Use mi_getopt_silent Yao Qi
2013-08-26 8:58 ` Agovic, Sanimir
2013-08-26 10:18 ` Yao Qi
2013-08-26 16:01 ` Pedro Alves
2013-08-26 16:22 ` Pedro Alves
2013-08-27 3:30 ` Yao Qi
2013-08-27 11:43 ` Pedro Alves
2013-07-29 9:33 ` [ping]: [PATCH 0/2] New option --skip-unavailable to -stack-list-XXX commands Yao Qi
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=521B84EE.70805@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.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