Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [patch 0/8] Download tracepoint locations when tracing is running
Date: Tue, 08 Nov 2011 06:00:00 -0000	[thread overview]
Message-ID: <4EB8C551.9090609@codesourcery.com> (raw)

Hi,
Current gdb/gdbserver only allows to download tracepoint before tracing
is started.  This patch set is about to teach gdb/gdbserver to be able
to download tracepoint locations even when tracing is run.  This feature
is quite useful to 1) adding new tracepoints after `tstart', 2) pending
tracepoints can be downloaded/installed in tracing (after this patch set
is applied, pending tracepoint works without much effort).

In order to achieve this feature, there are several points we should
address,
  #1 gdb should know whether remote stub supports this feature, so we
need a new qSupported feature "InstallInTrace" for this.  This is done
by patch 2/8.
  #2 gdb should be able to download tracepoint locations when they are
changed, and keep track of their 'status'.  This is done by patch 3/8.
  #3 gdbserver should be able to install tracepoint locations when
received from gdb.  This is done by patch 6/8 (patch 5/8 is a refactor
to gdbserver to prepare for 6/8).
  #4 remote stub may not always be able to receive tracepoint details,
and gdb has to download tracepoints when remote stub is ready.  This is
done by patch 3/8.

Patch 2/8 and 3/8 should be part of patch 4/8, but I split them to make
review more clear.  This patch set will be applied as a whole once it is
approved.

Patch 8/8 is about test cases.  Regression tested on x86-linux and
x86_64-linux.  All new added test cases pass on x86-linux, and two
kfails on x86_64-linux.  These two kfails are existing problem exposed
by new test cases.  I'll explain it in details in patch 8/8.

-- 
Yao (齐尧)


             reply	other threads:[~2011-11-08  6:00 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-08  6:00 Yao Qi [this message]
2011-11-08  6:08 ` [patch 1/8] Download tracepoint on location level Yao Qi
2011-11-09  3:34   ` Yao Qi
2011-11-10 14:54     ` Pedro Alves
2011-11-08  6:12 ` [patch 2/8] New remote feature InstallInTrace Yao Qi
2011-11-10 15:03   ` Pedro Alves
2011-11-08  6:21 ` [patch 3/8] New target hook `to_can_download_tracepoint_loc' Yao Qi
2011-11-10 15:11   ` Pedro Alves
2011-11-08  6:30 ` [patch 4/8] Download tracepoint locations and track its status Yao Qi
2011-11-09  3:47   ` Yao Qi
2011-11-10 15:51     ` Pedro Alves
2011-11-12  2:11       ` Yao Qi
2011-11-14 12:24         ` Pedro Alves
2011-11-08  6:33 ` [patch 5/8] refactor gdbserver on installing fast tracepoint Yao Qi
2011-11-10 15:57   ` Pedro Alves
2011-11-08  6:40 ` [patch 6/8] gdbserver - Install tracepoint when tracing is running Yao Qi
2011-11-08  8:20   ` Eli Zaretskii
2011-11-08  8:41     ` Yao Qi
2011-11-08 11:38       ` Eli Zaretskii
2011-11-10 16:53   ` Pedro Alves
2011-11-12  2:40     ` Yao Qi
2011-11-14 12:32       ` Pedro Alves
2011-11-08  6:43 ` [patch 7/8] Documentation changes Yao Qi
2011-11-08  8:37   ` Eli Zaretskii
2011-11-10 17:02   ` Pedro Alves
2011-11-12  3:09     ` Yao Qi
2011-11-08  6:56 ` [patch 8/8] Test cases Yao Qi
2011-11-10 17:16   ` Pedro Alves
2011-11-10 18:28   ` Pedro Alves
2011-11-12  3:35     ` Yao Qi
2011-11-14 13:00       ` Pedro Alves

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=4EB8C551.9090609@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