From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [ping]: [PATCH 0/5] MI notification on trace started/stopped (V3)
Date: Wed, 30 Jan 2013 04:00:00 -0000 [thread overview]
Message-ID: <51089AAF.7010908@codesourcery.com> (raw)
In-Reply-To: <1358838232-13319-1-git-send-email-yao@codesourcery.com>
On 01/22/2013 03:03 PM, Yao Qi wrote:
> Hello,
> 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.
>
> Patch 4/5 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 3/5 about. Patch 5/5 is to use this async remote
> notification 'Trace' and notify trace_changed observer.
>
> Patch 1/5 and 2/5 are the enhancement to the async remote
> notification, which is needed by the rest of patches in this series.
> Patch 1/5 adds "annex" for notification, which is helpful 1) to give
> more information on each event of notification, 2) to query supported
> notifications on "annex" level. Patch 2/5 teaches both GDB and
> GDBserver to query supported notifications and annexes in the other
> side so that 1) GDBserver doesn't send notifications that GDB doesn't
> understand, 2) GDB doesn't have to fetch status from the GDBserver if
> a certain notification is supported by GDBserver.
>
> This patch series is the V3 of this series. V2 was posted
> <http://sourceware.org/ml/gdb-patches/2012-12/msg00687.html>. Here
> are some changes in V3,
>
> - Introduce query mechanism on supported notifications
> - Introduce concept "annex" into remote notification,
> - Remove trace notes in MI notifications, suggested by Pedro in the
> review.
> - Combine observers 'trace-started' and 'trace-stoped' into one
> observer 'trace-changed'.
>
> Each patch is tested cumulatively on x86_64-linux with the combination
> {unix, native-gdbserver} x {sync, async}. Is it OK?
>
Ping. http://sourceware.org/ml/gdb-patches/2013-01/msg00505.html
--
Yao (é½å°§)
next prev parent reply other threads:[~2013-01-30 4:00 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-22 7:05 Yao Qi
2013-01-22 7:05 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-01-22 8:09 ` Eli Zaretskii
2013-01-22 8:41 ` Yao Qi
2013-01-22 10:26 ` Eli Zaretskii
2013-01-22 7:05 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-01-22 8:06 ` Eli Zaretskii
2013-01-22 7:05 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-01-22 8:06 ` Eli Zaretskii
2013-02-16 3:40 ` Yao Qi
2013-02-16 9:27 ` Eli Zaretskii
2013-03-29 17:17 ` Yao Qi
2013-03-31 0:39 ` Eli Zaretskii
2013-01-22 7:06 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-01-22 7:06 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-01-22 8:11 ` Eli Zaretskii
2013-01-30 4:00 ` Yao Qi [this message]
2013-02-07 12:41 ` [ping 2]: [PATCH 0/5] MI notification on trace started/stopped (V3) Yao Qi
2013-02-16 4:01 ` [PATCH 0/5] MI notification on trace started/stopped (V3.1) Yao Qi
2013-02-16 4:01 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-02-16 9:27 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-02-16 9:36 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-02-16 4:02 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-02-16 9:33 ` Eli Zaretskii
2013-03-11 9:26 ` Yao Qi
2013-03-11 16:59 ` Eli Zaretskii
2013-02-16 4:02 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-02-16 9:34 ` Eli Zaretskii
2013-02-25 3:14 ` ping: [PATCH 0/5] MI notification on trace started/stopped (V3.1) Yao Qi
2013-03-04 2:34 ` ping^2 : " Yao Qi
2013-04-02 2:33 ` [PATCH v4 0/5] MI notification on trace started/stopped Yao Qi
2013-04-02 3:15 ` [PATCH 2/5] Query supported notifications by qSupported Yao Qi
2013-04-02 3:58 ` [PATCH 3/5] async remote notification 'Trace' Yao Qi
2013-04-02 12:46 ` [PATCH 5/5] MI notification on trace stop: triggered by remote Yao Qi
2013-04-02 13:07 ` [PATCH 4/5] MI notification on trace started/stopped:basic Yao Qi
2013-04-02 13:30 ` [PATCH 1/5] Add annex in a async remote notification Yao Qi
2013-04-10 15:46 ` [PATCH v4 0/5] MI notification on trace started/stopped Yao Qi
2013-04-17 14:37 ` [ping 2]: " Yao Qi
2013-04-18 15:16 ` Pedro Alves
2013-04-18 16:14 ` Yao Qi
2013-06-04 9:20 ` 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=51089AAF.7010908@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