Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] New MI notification "=tsv-modified"
Date: Wed, 06 Feb 2013 14:31:00 -0000	[thread overview]
Message-ID: <51126935.6090501@redhat.com> (raw)
In-Reply-To: <51125685.4050406@codesourcery.com>

On 02/06/2013 01:11 PM, Yao Qi wrote:

> gdb:
> 
> 2013-02-06  Yao Qi  <yao@codesourcery.com>
> 
> 	* mi/mi-interp.c: Include "tracepoint.h".
> 	(mi_tsv_modified): Declare.
> 	(mi_tsv_created, mi_tsv_deleted): Update declaration.
> 	(mi_interpreter_init): Call observer_attach_tsv_modified.
> 	(mi_tsv_modified): New.
> 	(mi_tsv_created, mi_tsv_deleted): Update.
> 	* tracepoint.c (trace_variable_command): Call
> 	observer_notify_tsv_modified if the initial value of tsv is
> 	changed.
> 	(delete_trace_state_variable): Call
> 	observer_notify_tsv_deleted earlier.
> 	(trace_variable_command): Caller update.
> 	(create_tsv_from_upload): Likewise.
> 	* observer.sh: Declare "struct trace_state_variable".

> 
> gdb/testsuite:
> 
> 2013-02-06  Yao Qi  <yao@codesourcery.com>
> 
> 	* gdb.trace/mi-tsv-changed.exp (test_create_delete_tsv): Rename
> 	to ...
> 	(test_create_delete_modify_tsv): ... here.  New test on modifying
> 	the initial value of a tsv.

Thanks.  These parts are OK.

-- 
Pedro Alves


  reply	other threads:[~2013-02-06 14:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 15:44 Yao Qi
2013-01-30 17:17 ` Eli Zaretskii
2013-02-01 20:38 ` Pedro Alves
2013-02-02  8:29   ` Yao Qi
2013-02-04 17:55     ` Pedro Alves
2013-02-05 15:05       ` Yao Qi
2013-02-05 15:41         ` Pedro Alves
2013-02-06 13:12           ` Yao Qi
2013-02-06 14:31             ` Pedro Alves [this message]
2013-02-06 14:46               ` 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=51126935.6090501@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@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