Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Stan Shebs <stan_shebs@mentor.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Tracing notes and metadata
Date: Mon, 17 Oct 2011 16:39:00 -0000	[thread overview]
Message-ID: <83d3dvwphm.fsf@gnu.org> (raw)
In-Reply-To: <4E9C5112.9070705@mentor.com>

> Date: Mon, 17 Oct 2011 09:00:18 -0700
> From: Stan Shebs <stan_shebs@mentor.com>
> 
> With this patch, any arguments to tstart and tstop are recorded with the 
> trace run as free-form text, and reported as part of its status.  Also, 
> there is a trace-user variable (which is free form text which is 
> typically constant and you can set in your .gdbinit), and set/show 
> variables for the start and stop notes as well.
> 
> In addition, this patch adds start/stop timestamps and per-tracepoint 
> hit counts and traceframe usage.
> 
> The patch still needs testsuite and NEWS, but considering the user 
> interface tinkering, it seemed like a good idea to solicit feedback 
> before committing to all the details.

The documentation part is okay, but please add some overview of the
notes, to serve as the glue to the description of the commands.  As I
read the patch, I was wondering whether there's only one note that can
be set by either "tstart" or "tstop" (and then what happens if you
give arguments to "tstop" when "tstart" already provided a note?), or
two separate and independent notes (in which case why do we have
"trace-stop-notes", but no "trace-start-notes"?).  Instead of
disclosing all this piecemeal and leaving the reader with a reasonable
doubt, why not explain it once and for all?

Btw, didn't the socializing parties ask you for a way to _add_ to an
existing note, rather than overwriting it?  The way you designed it,
fixing a single typo requires retyping (or copy/pasting) the whole
thing, which sounds inconvenient.

Thanks.


  reply	other threads:[~2011-10-17 16:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-17 16:27 Stan Shebs
2011-10-17 16:39 ` Eli Zaretskii [this message]
2011-10-18  1:44   ` Stan Shebs
2011-11-03 15:18 ` 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=83d3dvwphm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=stan_shebs@mentor.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