As of the November 26th, 2007 test run the: ./TestRunner frysk.proc.dead.TestLinuxCore.testLinuxCoreFileStackTrace fails. This regression is probably due to commit: - Log ----------------------------------------------------------------- commit 62aaf4a1ee1f7a68ac9f8d694dd0bddba90c08ed Author: Sami Wagiaalla <swagiaal@redhat.com> Date: Fri Nov 23 15:48:53 2007 -0500 Reason for failure is now live stack traces are missing the option not to follow symlinks. So in this test run the live stack trace is: Task #24399 #0 0x0000000000400468 in fourth () from .../funit-stacks #1 0x00000000004004a0 in third () from .../funit-stacks #2 0x00000000004004c2 in second () from .../funit-stacks #3 0x00000000004004d5 in first () from .../funit-stacks #4 0x00000000004004e8 in main () from .../funit-stacks #5 0x00000038cba1e074 in __libc_start_main () from .../libc-2.7.so #6 0x00000000004003b9 in _start () from .../funit-stacks Core stack trace: Task #24399 #0 0x0000000000400468 in fourth () from .../funit-stacks #1 0x00000000004004a0 in third () from .../funit-stacks #2 0x00000000004004c2 in second () from .../funit-stacks #3 0x00000000004004d5 in first () from .../funit-stacks #4 0x00000000004004e8 in main () from .../funit-stacks #5 0x00000038cba1e074 in __libc_start_main () from .../libc.so.6 #6 0x00000000004003b9 in _start () from .../funit-stacks The test fail is: FAIL junit.framework.ComparisonFailure: Compare stack traces expected:<...-2.7.so...> but was:<....so.6...> If we look at libc [pmuldoon@localhost frysk-core]$ ls -lah /lib/libc.so.6 lrwxrwxrwx 1 root root 11 2007-11-12 10:51 /lib/libc.so.6 -> libc-2.7.so However this has always been the case. The linkmap stores the first entry (the symlink in the table, and therefore the corefile). This behavior has not changed since the corefile code existed.
Fixed: - Log ----------------------------------------------------------------- commit a53854d586aa13ef63c92fad41fc90d5e5ef7648 Author: Sami Wagiaalla <swagiaal@redhat.com> Date: Mon Nov 26 11:44:35 2007 -0500