From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [ping]: [PATCH] Teach -data-list-register-values to not include unavailable registers
Date: Mon, 17 Jun 2013 11:20:00 -0000 [thread overview]
Message-ID: <51BEE325.2090403@codesourcery.com> (raw)
In-Reply-To: <51B28F73.30301@codesourcery.com>
On 06/08/2013 09:57 AM, Yao Qi wrote:
> gdb:
>
> 2013-06-08 Pedro Alves<pedro@codesourcery.com>
> Yao Qi<yao@codesourcery.com>
>
> * NEWS: Mention the new option '--skip-unavailable' of command
> -data-list-register-values.
> * mi/mi-main.c (mi_cmd_data_list_register_values): Accept the
> --skip-unavailable option. Adjust to use output_register.
> (output_register): Add new 'skip_unavailable' parameter.
> Handle it.
>
> gdb/testsuite:
>
> 2013-06-08 Yao Qi<yao@codesourcery.com>
>
> * gdb.trace/mi-trace-unavailable.exp: Set tracepoint on 'foo'
> and set an action.
> (test_trace_unavailable): Test command -data-list-register-values
> in the context of traceframe and with option --skip-unavailable.
> * gdb.trace/trace-unavailable.c (foo): New.
> (main): Call it.
> * gdb.mi/gdb2549.exp: Update matching pattern.
Ping. http://sourceware.org/ml/gdb-patches/2013-06/msg00186.html
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-06-17 10:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 12:53 Yao Qi
2013-06-07 14:29 ` Eli Zaretskii
2013-06-07 20:09 ` Pedro Alves
2013-06-07 20:40 ` Pedro Alves
2013-06-08 3:48 ` Yao Qi
2013-06-08 5:21 ` Eli Zaretskii
2013-06-17 11:20 ` Yao Qi [this message]
2013-06-18 15:24 ` Tom Tromey
2013-06-19 10:03 ` Yao Qi
2013-06-19 19:07 ` Tom Tromey
2013-06-20 4:59 ` 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=51BEE325.2090403@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