Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] MI notification on record started and stopped
Date: Fri, 14 Sep 2012 02:54:00 -0000	[thread overview]
Message-ID: <50529C21.5020909@codesourcery.com> (raw)
In-Reply-To: <83r4q5vne6.fsf@gnu.org>

On 09/14/2012 01:33 AM, Eli Zaretskii wrote:
> Sorry, I don't understand: is that parameter the OS PID of the
> inferior, or is that the inferior number displayed in the first column
> of the "info inferiors" output?

The latter.  The notification is like '=record-started,thread-group="i1"'.

-- 
Yao


  reply	other threads:[~2012-09-14  2:54 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-12  7:16 [PATCH 0/2] Two MI notifications on TSV and process record Yao Qi
2012-09-12  7:16 ` [PATCH 2/2] MI notification on record started and stopped Yao Qi
2012-09-12 17:52   ` Eli Zaretskii
2012-09-13  8:57     ` Yao Qi
2012-09-13 17:33       ` Eli Zaretskii
2012-09-14  2:54         ` Yao Qi [this message]
2012-09-14  9:49           ` Eli Zaretskii
2012-09-14 11:45             ` Yao Qi
2012-09-14 12:09               ` Pedro Alves
2012-09-14 13:14                 ` Yao Qi
2012-09-14 14:13                   ` Pedro Alves
2012-09-21  1:47                     ` [committed]: " Yao Qi
2012-09-21  6:58                       ` Regression for gdb.mi/mi-reverse.exp [Re: [committed]: [PATCH 2/2] MI notification on record started and stopped] Jan Kratochvil
2012-09-21  7:26                         ` Yao Qi
2012-09-14 13:30               ` [PATCH 2/2] MI notification on record started and stopped Eli Zaretskii
2012-09-12 18:07   ` Tom Tromey
2012-09-12 19:04     ` Pedro Alves
2012-09-12 19:01   ` Pedro Alves
2012-09-12  7:16 ` [PATCH 1/2] MI notification on tsv created and deleted Yao Qi
2012-09-12 17:48   ` Eli Zaretskii
2012-09-18 12:19     ` [committed]: " Yao Qi
2012-09-13 20:17   ` 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=50529C21.5020909@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=eliz@gnu.org \
    --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