This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[ping]: [PATCH 0/3] MI notification on trace started/stopped (V2)


On 12/19/2012 06:54 PM, Yao Qi wrote:
Hello,
This patch series adds the notifications of 'trace-started' and
'trace-stopped', which are emitted when

   1) trace is started or stopped by commands in GDB,
   2) trace is stopped due to some reasons in the remote stub, such as
trace buffer full.

With these notifications, MI front-end can show the status of trace
up to date.

Patch 1/3 is to address #1, adding new MI notifications and
notifying observers when the commands are called.  #2 needs more work
here, because GDB doesn't know the trace is stopped in the remote
stub.  So we need an async remote notification 'Trace' to tell GDB.
That is what patch 2/3 about.  Patch 3/3 is to use this async remote
notification 'Trace' and notify trace_stopped observer.


Ping. http://sourceware.org/ml/gdb-patches/2012-12/msg00687.html


--
Yao (éå)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]