Better testing for Stackwalk

[GoogleCodeExporter]

I was thinking about different ways to test Stackwalk.  One idea I had was
to walk the test process' own stack.  I threw this together, which makes a
bunch of recursive calls to verify that Stackwalker returns the right
number of frames on x86.

Original issue reported on code.google.com by mmento...@gmail.com on 7 Sep 2006 at 8:58

Attachments:

• airbag.18.1.patch

[GoogleCodeExporter]

Original comment by mmento...@gmail.com on 25 Sep 2006 at 4:41

[GoogleCodeExporter]

This is a new version that's capable of doing the self-test on both x86 and 
ppc.  I
don't want to check this in (or if we check it in, I don't want to make the 
test part
of the standard "make check" suite) because certain optimizations can flatten 
the
recursion.  This causes CountCallerFrames to correctly return a smaller number 
than
the logical recursion depth, and is treated as a failure, even though the stack 
is in
good shape and was fully walked successfully.

Original comment by mmento...@gmail.com on 25 Sep 2006 at 4:43

Attachments:

• stackwalker_selftest.cc

[GoogleCodeExporter]

Conditional testing

Original comment by mmento...@gmail.com on 25 Sep 2006 at 7:42

Attachments:

• airbag.16.2.patch

[GoogleCodeExporter]

Checked in, [35].  This test is disabled by default.  Enable it by configuring 
with
--enable-selftest.

Original comment by mmento...@gmail.com on 25 Sep 2006 at 9:16

[GoogleCodeExporter]

Original comment by mmento...@gmail.com on 25 Sep 2006 at 9:17

• Changed state: Fixed