From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH 0/5 V8] MI notification on trace started/stopped
Date: Fri, 24 Jan 2014 09:43:00 -0000 [thread overview]
Message-ID: <1390556465-28796-1-git-send-email-yao@codesourcery.com> (raw)
Hello,
This is the V8 of the patch series for "MI notification on trace
started and stopped". In V8, the changes are:
- Treat notification as a feature in qSupported, to get to know
a certain notification is supported or not. It saves much
code.
- Call observer_notify_trace_changed only when GDB gets async
remote notification Trace, so that the notification order is
consistent in two sides (GDB side and GDBserver side).
- Consume some notification events on some points in all stop
mode. See patch 1/5.
Patch 2/5 is about querying supported notifications. Patch 3/5
is to add new async remote notification trace. Patch 4/5 is to
add new MI notification on trace started and stopped. Patch 5/5
is to add the test cases.
They are tested on x86_64-linux with
{unix, native-gdbserver} x {sync, async}. Is it OK?
V7 can be found https://sourceware.org/ml/gdb-patches/2013-12/msg00495.html
*** BLURB HERE ***
Yao Qi (5):
Process notifications when reply is got
Query supported notifications by qSupported
async remote notification 'Trace'.
MI notification on trace started/stopped
New test case mi-trace-changed.exp
gdb/Makefile.in | 5 +-
gdb/NEWS | 5 +
gdb/doc/gdb.texinfo | 26 +++++
gdb/doc/observer.texi | 6 +
gdb/gdbserver/notif.c | 44 ++++++++
gdb/gdbserver/notif.h | 6 +
gdb/gdbserver/server.c | 15 +++-
gdb/gdbserver/tracepoint.c | 35 ++++++
gdb/mi/mi-cmds.c | 6 +-
gdb/mi/mi-interp.c | 22 ++++
gdb/mi/mi-main.h | 2 +
gdb/remote-notif-trace.c | 79 ++++++++++++++
gdb/remote-notif.c | 57 +++++++++-
gdb/remote-notif.h | 14 +++-
gdb/remote.c | 47 +++++++-
gdb/testsuite/gdb.trace/mi-trace-changed.exp | 149 ++++++++++++++++++++++++++
16 files changed, 504 insertions(+), 14 deletions(-)
create mode 100644 gdb/remote-notif-trace.c
create mode 100644 gdb/testsuite/gdb.trace/mi-trace-changed.exp
--
1.7.7.6
next reply other threads:[~2014-01-24 9:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-24 9:43 Yao Qi [this message]
2014-01-24 9:43 ` [PATCH 1/5] Process notifications when reply is got Yao Qi
2014-01-24 9:43 ` [PATCH 5/5] New test case mi-trace-changed.exp Yao Qi
2014-01-24 9:43 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2014-01-24 9:43 ` [PATCH 4/5] MI notification on trace started/stopped Yao Qi
2014-01-24 9:43 ` [PATCH 3/5] async remote notification 'Trace' 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=1390556465-28796-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