This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Print trace state variables
- From: Hui Zhu <teawater at gmail dot com>
- To: Stan Shebs <stan at codesourcery dot com>
- Cc: gdb-patches at sourceware dot org
- Date: Mon, 13 Dec 2010 20:30:47 +0800
- Subject: Re: [PATCH] Print trace state variables
- References: <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.
>
>
>
>