This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[RFC] MI notification on trace stop: triggered by remote
- From: Yao Qi <yao at codesourcery dot com>
- To: <gdb-patches at sourceware dot org>
- Date: Thu, 8 Nov 2012 16:39:19 +0800
- Subject: [RFC] MI notification on trace stop: triggered by remote
Hi,
In current GDB, when tracing in remote stub is stopped, GDB doesn't
know this unless it sends a qTStatus packet to query about it. This
patch set adds a new rsp notification %NTrace, which can notify GDB
when tracing is stopped. This patch set addresses the issues I
mentioned in this mail
[1] [PATCH] MI notification on trace started/stopped:basic
http://sourceware.org/ml/gdb-patches/2012-11/msg00175.html
On the other hand, it is the first real use case of 'general rsp
notification' posted here,
[2] [RFC 0/7 V3]A general notification in GDB RSP
http://sourceware.org/ml/gdb-patches/2012-10/msg00404.html
This patch set doesn't include document bits, and still need
polish here and there. However, they are in shape, and I post them
here to get some comments.
With rsp notification and mi notification , the flow can be shown by
the following diagram,
GDBserver GDB Eclipse
%NTrace =trace-stopped
buffer full --------> ---------------->
qTStatus -trace-status
<-------- <---------------- get details
Patch 1/2 defines a new rsp notification %NTrace, and patch 2/2 sends
"=trace-stopped" once %NTrace is got.
Of course, this patch set depends on [1] and [2].