This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] Add CTF support to GDB [3/4] ctf target
- From: Tom Tromey <tromey at redhat dot com>
- To: Hui Zhu <hui_zhu at mentor dot com>
- Cc: <gdb-patches at sourceware dot org>
- Date: Thu, 29 Nov 2012 13:46:48 -0700
- Subject: Re: [PATCH] Add CTF support to GDB [3/4] ctf target
- References: <50AC323F.1070907@mentor.com>
>>>>> "Hui" == Hui Zhu <hui_zhu@mentor.com> writes:
Hui> It add a new target ctf like the tfile target to read the ctf file.
Hui> After use this target open the ctf dir, you can use tfind to select
Hui> the ctf event. Each field inside this event will add to GDB as a
Hui> internalvar. And tdump will show all of them. And you can use python
Hui> read the value of them.
Can you explain the internalvar feature a little? Why is it needed?
How are these variables named? What do they represent? Are they
different from the saved trace data somehow? I notice this feature
isn't in the documentation at all -- I think that is required, perhaps
with an example.
Tom