Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Print trace state variables
Date: Mon, 13 Dec 2010 12:31:00 -0000	[thread overview]
Message-ID: <AANLkTi=88p9kpRo8go7=Pkz-w64-LZR7AwMQ6HeqOvgb@mail.gmail.com> (raw)
In-Reply-To: <4D015A4A.7040500@codesourcery.com>

Cool!

This function is really great!

Thanks,
Hui

On Fri, Dec 10, 2010 at 06:38, Stan Shebs <stan@codesourcery.com> wrote:
> This patch remedies an oversight in recent tracepoint work, by adding
> printing of trace state variables.  While you can see tsv values using "info
> tvariables", it's much more useful to be able to include them in print
> commands and expressions in general; you can then display them in different
> formats, or compute the difference between a tsv and some other value.  The
> manual already documents this as working, only the code to do it has been
> missing. :-)
>
> This has been in CodeSourcery's version for some time, but I set it aside
> for awhile because it seemed a little kludgy to add a tracepoint-specific
> case into general evaluation.  On the plus side, its effect is localized,
> and should be safe for a 7.2 update release, where it will be useful for
> work on trace support in Eclipse.  There are no regressions testing with
> either i386-linux native or GDBserver.
>
> If this seems reasonable, I'll put in both trunk and 7.2 branch.
>
> Stan
>
> 2010-12-08  Stan Shebs <stan@codesourcery.com>
>
>    * value.c (value_of_internalvar): Add case for trace state
>    variables.
>
>    * gdb.trace/tsv.exp: Test print command on trace state variables.
>
>
>
>


      parent reply	other threads:[~2010-12-13 12:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-09 22:38 Stan Shebs
2010-12-10 11:27 ` Joel Brobecker
2010-12-10 14:04   ` Stan Shebs
2010-12-10 16:35   ` Marc Khouzam
2010-12-10 20:00     ` Tom Tromey
2010-12-11  5:28       ` Joel Brobecker
2010-12-11  5:55 ` Joel Brobecker
2010-12-13  5:56   ` Stan Shebs
2010-12-13 13:00   ` Pedro Alves
2010-12-14 16:13   ` Tom Tromey
2010-12-13 12:31 ` Hui Zhu [this message]

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='AANLkTi=88p9kpRo8go7=Pkz-w64-LZR7AwMQ6HeqOvgb@mail.gmail.com' \
    --to=teawater@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@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