[PATCH 0/2] Test case on entry values

[Yao Qi <yao@codesourcery.com>]

Hi,
In the review of the patch which adds '--skip-unavailable' to skip
unavailable locals and arguments, Pedro pointed that "entry value" should be
considered too.  The code is not hard, but the test case is harder than the
code.  We have to make sure that 1) necessary DIEs are generated, 2) set up
a case that argument is available but entry value is not.

We choose the test to arguments and entry values when GDB is examining trace
frames, because something can be unavailable.  This situation is not tested
in current testsuite, and this test can be reviewed committed independently.

Patch 1/2 is to generate dwarf using Dwarf Assembler to test "entry values"
are shown correctly.  At this point, gdb.trace/entry-values.exp is still
a dwarf test, nothing to do with trace.  Patch 2/2 is to use tracepoint,
to collect data, to test what happen when argument is available and entry
value is not.

Most of gdb.trace/etnry-values.exp is a dwarf test, and we can move them
to gdb.dwarf2 and copy necessary bits in gdb.trace.  I didn't do that
because it will cause some duplication.

*** BLURB HERE ***

Yao Qi (2):
  Test case for entry values.
  Test entry values in trace frame

 gdb/testsuite/gdb.trace/entry-values.c   |   50 ++++++
 gdb/testsuite/gdb.trace/entry-values.exp |  274 ++++++++++++++++++++++++++++++
 gdb/testsuite/lib/dwarf.exp              |    8 +
 3 files changed, 332 insertions(+), 0 deletions(-)
 create mode 100644 gdb/testsuite/gdb.trace/entry-values.c
 create mode 100644 gdb/testsuite/gdb.trace/entry-values.exp

-- 
1.7.7.6