From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Kwok Cheung Yeung <kcy@codesourcery.com>, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH] Support for enabling/disabling tracepoints while a trace experiment is running
Date: Wed, 11 May 2011 09:14:00 -0000 [thread overview]
Message-ID: <201105111014.07919.pedro@codesourcery.com> (raw)
In-Reply-To: <4DC840FE.6050408@codesourcery.com>
On Monday 09 May 2011 20:31:10, Kwok Cheung Yeung wrote:
> gdb/
> * breakpoint.c (disable_breakpoint): Disable all locations
> associated with a tracepoint on target if a trace experiment is
> running.
> (disable_command): Disable a specific tracepoint location on target if
> a trace experiment is running.
> (do_enable_breakpoint): Enable all locations associated with a
> tracepoint on target if a trace experiment is running.
> (enable_command) Enable a specific tracepoint location on target if a
> trace experiment is running.
> * target.c (update_current_target): Add INHERIT and de_fault clauses for
> to_supports_enable_disable_tracepoint, to_enable_tracepoint and
> to_disable_tracepoint.
> * target.h: Add declaration of struct bp_location.
> (struct target_ops): Add new functions
> to_supports_enable_disable_tracepoint, to_enable_tracepoint and
> to_disable_tracepoint to target operations.
> (target_supports_enable_disable_tracepoint): New macro.
> (target_enable_tracepoint): New macro.
> (target_disable_tracepoint): New macro.
> * remote.c (struct remote_state): Add new field.
> (remote_enable_disable_tracepoint_feature): New.
> (remote_protocol_features): Add new entry.
> (remote_supports_enable_disable_tracepoint): New.
> (remote_enable_tracepoint): New.
> (remote_disable_tracepoint): New.
> (init_remote_ops): Add remote_enable_tracepoint,
> remote_disable_tracepoint and remote_supports_enable_disable_tracepoint
> to remote operations.
> * tracepoint.c (start_tracing): Allow tracing to start without any
> tracepoints enabled with just a warning if they can be re-enabled
> later.
Okay.
>
> gdb/gdbserver/
> * server.c (handle_query): Add EnableDisableTracepoints to the list
> of supported features.
> * tracepoint.c (clear_installed_tracepoints): Uninstall disabled
> tracepoints.
> (cmd_qtenable_disable): New.
> (cmd_qtstart): Install tracepoints even if disabled.
> (handle_tracepoint_general_set): Add call to cmd_qtenable_disable on
> receiving a QTEnable or QTDisable packet.
> (gdb_collect): Skip data collection if fast tracepoint is disabled.
> (ust_marker_to_static_tracepoint): Do not ignore disabled static
> tracepoints.
> (gdb_probe): Skip data collection if static tracepoint is disabled.
Okay.
--
Pedro Alves
next prev parent reply other threads:[~2011-05-11 9:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 17:27 Kwok Cheung Yeung
2011-05-05 17:48 ` Pedro Alves
2011-05-05 18:29 ` Kwok Cheung Yeung
2011-05-05 18:52 ` Eli Zaretskii
2011-05-05 23:13 ` Kwok Cheung Yeung
2011-05-05 23:47 ` Stan Shebs
2011-05-06 10:33 ` Eli Zaretskii
2011-05-09 19:31 ` Kwok Cheung Yeung
2011-05-09 19:35 ` Eli Zaretskii
2011-05-11 9:14 ` Pedro Alves [this message]
2011-05-06 17:42 ` Tom Tromey
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=201105111014.07919.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=kcy@codesourcery.com \
/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