#13 Incomplete stack traces

[Christoph Schwarz]

Stack traces frequently end after the first frame

To reproduce:

coregrind\valgrind.exe memcheck\tests\windows\memcheck-x86-windows.exe

Actual output:

....
Test read-after-free 1
==6620== Invalid read of size 1
==6620==    at 0x70301CD8: strlen (mc_replace_strmem.c:482)
==6620==    by 0x41FFE98: ???
==6620==    by 0x402830: ??? (memcheck.c:23)
==6620==    by 0x4013EA: __tmainCRTStartup (crtexe.c:309)
==6620==    by 0x41FFFCC: ???
==6620==  Address 0x4201240 is 0 bytes inside a block of size 32 free'd
==6620==    at 0x703012B8: free (vg_replace_malloc.c:456)
==6620==
Test read-after-free 2
...

Expected output:

....
Test read-after-free 1
==6620== Invalid read of size 1
==6620==    at 0x70301CD8: strlen (mc_replace_strmem.c:482)
==6620==    by 0x41FFE98: ???
==6620==    by 0x402830: ??? (memcheck.c:23)
==6620==    by 0x4013EA: __tmainCRTStartup (crtexe.c:309)
==6620==    by 0x41FFFCC: ???
==6620==  Address 0x4201240 is 0 bytes inside a block of size 32 free'd
==6620==    at 0x703012B8: free (vg_replace_malloc.c:456)
==6620==    by 0x402830: test_read_after_free_1 (memcheck.c:16)
==6620==    by 0x4013EA: __tmainCRTStartup (crtexe.c:309)
==6620==
Test read-after-free 2
...

See also [#1] and [#2].