Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Kwok Cheung Yeung <kcy@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Support for enabling/disabling tracepoints while a trace experiment is running
Date: Fri, 06 May 2011 17:42:00 -0000	[thread overview]
Message-ID: <m3bozfwwtq.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4DC2DDEF.10600@codesourcery.com> (Kwok Cheung Yeung's message of	"Thu, 05 May 2011 18:27:11 +0100")

>>>>> ">" == Kwok Cheung Yeung <kcy@codesourcery.com> writes:

>> This patch adds support for enabling or disabling tracepoints while
>> an experiment is running, by sending a new remote command to the
>> gdbserver whenever this happens.

Just one nit...

>> Index: gdb/NEWS
[...]
>>    Initial support for the OpenCL C language (http://www.khronos.org/opencl)
>>    has been integrated into GDB.

>> +* Tracepoints can now be enabled and disabled at any time after a trace
>> +  experiment has been started using the standard "enable" and "disable"
>> +  commands.  If a trace experiment is started with no enabled
>> +  tracepoints, then a warning will be printed but the experiment will
>> +  proceed anyway.

I think these additions are in the "in 7.3" section but they should be
in the "since 7.3" section.

Tom


      parent reply	other threads:[~2011-05-06 17:42 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
2011-05-06 17:42 ` Tom Tromey [this message]

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=m3bozfwwtq.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --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