From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/5] New MI command -trace-frame-collected
Date: Fri, 07 Jun 2013 13:07:00 -0000 [thread overview]
Message-ID: <1370610493-26468-1-git-send-email-yao@codesourcery.com> (raw)
Hi,
In a given traceframe, there are explicitly collected variables,
registers, trace state variables, memories, and computed expressions.
In MI, we don't have a command to dump these contents, and this patch
adds -trace-frame-collected to do so.
Patch 4/5 is the major part of this series, and patch 5/5 is the test
to -trace-frame-collected. GDB needs to know what trace state
variables are collected in a traceframe, so we extended the
qXfer:traceframe-info object to report the set of collected trace
state variables in the current traceframe. That is what patch 3/5 does.
Patch 1/5, and 2/5 code refactor.
The whole series are tested on x86_64-linux with native and gdbserver.
*** BLURB HERE ***
Yao Qi (5):
Remove global variable tracepoint_list and stepping_list.
Move code to get_traceframe_location.
Add id of TSV into traceframe_info.
New MI command -trace-frame-collected
New test: gdb.trace/mi-trace-frame-collected.exp
gdb/NEWS | 9 +
gdb/breakpoint.c | 2 -
gdb/common/filestuff.c | 2 -
gdb/common/gdb_vecs.h | 2 +
gdb/ctf.c | 12 +
gdb/doc/gdb.texinfo | 122 ++++++++-
gdb/dwarf2loc.c | 2 -
gdb/features/traceframe-info.dtd | 5 +-
gdb/gdbserver/tracepoint.c | 7 +
gdb/mi/mi-cmds.c | 2 +
gdb/mi/mi-cmds.h | 1 +
gdb/mi/mi-main.c | 296 +++++++++++++++++++-
gdb/remote.c | 2 +-
.../gdb.trace/mi-trace-frame-collected.exp | 157 ++++++++++
gdb/tracepoint.c | 308 +++++++++++++-------
gdb/tracepoint.h | 53 ++++-
16 files changed, 860 insertions(+), 122 deletions(-)
create mode 100644 gdb/testsuite/gdb.trace/mi-trace-frame-collected.exp
--
1.7.7.6
next reply other threads:[~2013-06-07 13:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-07 13:07 Yao Qi [this message]
2013-06-07 13:07 ` [PATCH 2/5] Move code to get_traceframe_location Yao Qi
2013-06-07 21:09 ` Pedro Alves
2013-06-07 13:07 ` [PATCH 3/5] Add id of TSV into traceframe_info Yao Qi
2013-06-07 14:39 ` Eli Zaretskii
2013-06-08 11:06 ` Yao Qi
2013-06-07 13:07 ` [PATCH 5/5] New test: gdb.trace/mi-trace-frame-collected.exp Yao Qi
2013-06-07 13:07 ` [PATCH 1/5] Remove global variable tracepoint_list and stepping_list Yao Qi
2013-06-07 20:50 ` Pedro Alves
2013-06-07 13:07 ` [PATCH 4/5] New MI command -trace-frame-collected Yao Qi
2013-06-13 1:29 ` [PATCH 0/6 V2] " Yao Qi
2013-06-13 1:29 ` [PATCH 5/6] " Yao Qi
2013-06-13 14:27 ` Eli Zaretskii
2013-06-14 9:52 ` Yao Qi
2013-06-14 12:34 ` Eli Zaretskii
2013-06-17 10:21 ` Yao Qi
2013-06-17 15:48 ` Eli Zaretskii
2013-06-18 14:09 ` Yao Qi
2013-06-18 17:24 ` Eli Zaretskii
2013-06-25 17:31 ` Pedro Alves
2013-06-26 8:29 ` Yao Qi
2013-06-26 11:22 ` Pedro Alves
2013-06-13 1:29 ` [PATCH 2/6] Emit error in tdump command when traceframe is not selected Yao Qi
2013-06-25 15:32 ` Pedro Alves
2013-06-13 1:29 ` [PATCH 4/6] Add id of TSV into traceframe_info Yao Qi
2013-06-13 3:40 ` Eli Zaretskii
2013-06-25 16:18 ` Pedro Alves
2013-06-26 8:19 ` Yao Qi
2013-06-13 1:29 ` [PATCH 6/6] New test: gdb.trace/mi-trace-frame-collected.exp Yao Qi
2013-06-25 18:42 ` Pedro Alves
2013-06-26 10:32 ` Yao Qi
2013-06-13 1:29 ` [PATCH 3/6] Move code to get_traceframe_location Yao Qi
2013-06-25 15:43 ` Pedro Alves
2013-06-13 2:46 ` [PATCH 1/6] Remove global variable tracepoint_list and stepping_list Yao Qi
2013-06-25 15:28 ` Pedro Alves
2013-06-24 15:25 ` [ping]: [PATCH 0/6 V2] New MI command -trace-frame-collected 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=1370610493-26468-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