Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: "Abid, Hafiz" <hafiz_abid@mentor.com>
Cc: gdb-patches@sourceware.org, marc.khouzam@ericsson.com
Subject: Re: [Patch] Get trace file name when using 'target tfile'
Date: Wed, 13 Feb 2013 16:34:00 -0000	[thread overview]
Message-ID: <511BC083.2050803@redhat.com> (raw)
In-Reply-To: <1360766298.2842.0@abidh-ubunto1104>

On 02/13/2013 02:38 PM, Abid, Hafiz wrote:

> diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
> index e3f336e..e8ac8c5 100644
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -32094,6 +32094,10 @@ The value of the disconnected tracing flag.  @code{1} means that
>  tracing will continue after @value{GDBN} disconnects, @code{0} means
>  that the trace run will stop.
>  
> +@item trace-file
> +The filename of the trace file being examined.  This field is
> +optional, and only present when examining a trace file.

The docs bits need Eli's approval.  Obviously it looks
good to me. :-)  Though, since this adds an MI attribute, it
should have a corresponding NEWS entry too.

I'd be good to tweak the MI tfile tests to check this new field.
Can you do that please?

> +  if (ts->from_file)

  if (ts->from_file != NULL)

> +    ui_out_field_string (uiout, "trace-file", ts->from_file);


> +  /* We know we're working with a file. Record its name.  */

Double space. ----------------------------^

Otherwise this is OK.

-- 
Pedro Alves


  reply	other threads:[~2013-02-13 16:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-13 14:38 Abid, Hafiz
2013-02-13 16:34 ` Pedro Alves [this message]
2013-02-13 17:59 ` Eli Zaretskii
2013-02-14  3:17 ` Yao Qi
2013-02-14 14:34   ` Pedro Alves
2013-02-14 15:49     ` Abid, Hafiz
2013-02-14 15:57       ` Pedro Alves
2013-02-14 22:02       ` Eli Zaretskii
2013-02-15 10:15         ` Abid, Hafiz

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=511BC083.2050803@redhat.com \
    --to=palves@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hafiz_abid@mentor.com \
    --cc=marc.khouzam@ericsson.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