Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/2] New option --skip-unavailable to -stack-list-XXX commands
Date: Wed, 03 Jul 2013 01:48:00 -0000	[thread overview]
Message-ID: <1372816106-15942-1-git-send-email-yao@codesourcery.com> (raw)

Hi,
This patch series add new option '--skip-unavailable' to MI commands
'-stack-list-{locals, arguments, variables}'.  This option is optional,
and when it is used, locals or arguments whose values are not available
are not listed.  It is useful when the MI front-end is not interested in
unavailable values.

The patch 1/2 is a refactor patch, use mi_getopt in
mi_cmd_stack_list_locals and mi_cmd_stack_list_variables, so it is
easier to add new option patch 2/2.  Patch 2/2 is the major part of this
series.

Regression tested on x86_64-linux.

Note that this patch is for MI, but the idea that skipping unavailable
locals and arguments can be applied to CLI too.  We can invent new CLI
commands on top of 'info locals' and 'info args' to display available
locals or arguments.  This piece of work is not included in this
series.

*** BLURB HERE ***

Yao Qi (2):
  Use mi_getopt in mi_cmd_stack_list_locals and mi_cmd_stack_list_variables
  Add options to skip unavailable locals

 gdb/doc/gdb.texinfo                              |   17 ++-
 gdb/mi/mi-cmd-stack.c                            |  256 ++++++++++++++++------
 gdb/testsuite/gdb.trace/mi-trace-unavailable.exp |    9 +
 gdb/valprint.c                                   |    8 +-
 gdb/valprint.h                                   |    2 +
 gdb/value.c                                      |   20 ++
 gdb/value.h                                      |    4 +
 7 files changed, 246 insertions(+), 70 deletions(-)

-- 
1.7.7.6


             reply	other threads:[~2013-07-03  1:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-03  1:48 Yao Qi [this message]
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
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-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-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=1372816106-15942-1-git-send-email-yao@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    /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