Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH] traceframe_changed observer and MI notification
Date: Mon, 10 Sep 2012 18:52:00 -0000	[thread overview]
Message-ID: <87k3w1d82y.fsf@fleche.redhat.com> (raw)
In-Reply-To: <1346404195-20864-1-git-send-email-yao@codesourcery.com> (Yao	Qi's message of "Fri, 31 Aug 2012 17:09:55 +0800")

>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:

Yao> Regression tested on x86_64-linux native and gdbserver.  OK?

The idea seems fine to me.

Yao> +@item =traceframe-changed,num=@var{tfnum},tracepoint=@var{tpnum}
Yao> +@itemx =traceframe-changed,end
Yao> +Reports that the traceframe is changed and its number is @var{tfnum}.
Yao> +or @value{GDBN} stops examining traceframes and resumes live debugging.
Yao> +The number of the tracepoint associated with this traceframe is
Yao> +@var{tpnum}.

That should be a comma and not a period before "or".

Yao> +static void
Yao> +mi_traceframe_changed (int tfnum, int tpnum)

This function needs an introductory comment.
It can be brief.

Yao> +  target_terminal_ours ();
Yao> +
Yao> +  if (mi_suppress_notification.traceframe)
Yao> +    return;

It seems to me that checking suppression first is probably better.

Tom


  parent reply	other threads:[~2012-09-10 18:52 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-31  9:10 Yao Qi
2012-09-07  6:59 ` [ping]: " Yao Qi
2012-09-10 18:52 ` Tom Tromey [this message]
2012-09-11 13:38   ` Yao Qi
2012-09-11 15:28     ` Tom Tromey
2012-09-18  0:09 ` Yao Qi
2012-09-18  6:53   ` Eli Zaretskii
2012-09-18  7:24     ` Yao Qi
2012-09-18  8:01       ` Eli Zaretskii
2012-09-18  8:48         ` Yao Qi
2012-09-18  9:42           ` Eli Zaretskii
2012-09-18 11:42             ` 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=87k3w1d82y.fsf@fleche.redhat.com \
    --to=tromey@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