Adding untrusted crash dump / stack trace tests.

tests/untrusted_crash_dump/untrusted_crash_dump_test_glibc.golden

Index: tests/untrusted_crash_dump/untrusted_crash_dump_test_glibc.golden
diff --git a/tests/untrusted_crash_dump/untrusted_crash_dump_test_glibc.golden b/tests/untrusted_crash_dump/untrusted_crash_dump_test_glibc.golden
new file mode 100644
index 0000000000000000000000000000000000000000..edd014e3d3b5a5e68e02456413054d3cb3db6e99
--- /dev/null
+++ b/tests/untrusted_crash_dump/untrusted_crash_dump_test_glibc.golden
@@ -0,0 +1,9 @@
+layer5 at untrusted_crash_dump_test.c:21
+layer4 at untrusted_crash_dump_test.c:26
+CallMe at untrusted_crash_dump_lib.c:9
+layer3 at untrusted_crash_dump_test.c:30
+layer2 at untrusted_crash_dump_test.c:34
+layer1 at untrusted_crash_dump_test.c:38
+main at untrusted_crash_dump_test.c:45
+__libc_start_main at libc-start.c:227

[Mark Seaborn, 2012/02/09 22:24:55]

I don't like having glibc line numbers in golden files.  It will just create
problems for anyone updating DEPS or running the tests on different libc
versions.

My suggestion:  Have a Python test script that does this:

 * imports decode_dump.py
 * Calls a function in decode_dump to get an unformatted backtrace as a Python
list.
 * Assert that the list starts with the function names "layer5", "layer4" etc.
with the filename "untrusted_crash_dump_test.c".
 * Don't embed line numbers in the test.  But you can check a couple of line
numbers by reading the line from the file (using Python's linecache) and
asserting that the line contains a special comment.
 * Also check that you can format the backtrace without getting a Python
exception (but don't look at the formatted backtrace itself).

+_start at start.c:39