This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
[PATCH 0/5] Look for the last matched V block in trace frame
- From: Yao Qi <yao at codesourcery dot com>
- To: <gdb-patches at sourceware dot org>
- Date: Thu, 7 Mar 2013 10:41:40 +0800
- Subject: [PATCH 0/5] Look for the last matched V block in trace frame
When testing CTF patches on reading TSV from traceframes, I find we don't
have such test case in testsuite. gdb.trace/tsv.exp is only about reading
TSV from GDB itself, instead of from trace frames. I modified the
gdb.trace/tsv.exp to test that the same TSV should be the same on value when
it is read from GDB itself, trace frame in the remote target or trace frame in
the tfile target (or in the ctf target). See patch 1/5 and 2/5.
The modified test exposes a bug that GDB only looks for the first matched
TSV in a traceframe, while there may be multiple V blocks for this TSV in
one trace frame, and the value only in the lats one is up to date. Patch
3/5 is to fix this issue by looking for the last matched TSV. Patch 1/5 ~
3/5 can be applied on mainline.
Patch 4/5 is the test on ctf target, and patch 5/5 is the fix to the same
problem on ctf target. Both of them depend on the "CTF Support" patch
series. They two can be merged to "CTF Support" patch series in the next
review iteration if patch 1/5 - 3/5 go in.
--
1.7.7.6