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]

Re: [PATCH 0/6 V5] MI notification on trace started/stopped


On 08/19/2013 09:55 AM, Yao Qi wrote:
This is the V5 of this patch series, and the changes in V5 are:

  - Move 'notif_queue' to remote_state, which is done by patch 1/6.
  - Store the supported status of each annex in remote_state too.  It
    is the major change in patch 3/6 compared with V4.
  - some small fixes in code and comments.

Patch 1/6 can be regarded as a refactor patch, so it can be approved
separately.  Patch 5/6 adds MI notifications when command 'tstart'
and 'tstop' is typed in MI, it is a typical MI patch, and can be
approved separately too.

Regression tested them on x86_64-linux with
{unix, native-gdbserver} x {sync, async}.  Is it OK?

Below is the introduction of this series.  People who are
familiar with this series, please skip it.

This patch series adds the MI 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.

V4 can be found here

   [PATCH v4 0/5] MI notification on trace started/stopped
   http://sourceware.org/ml/gdb-patches/2013-04/msg00019.html

Ping.  https://sourceware.org/ml/gdb-patches/2013-08/msg00484.html

--
Yao (éå)


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