1) testStressMultiThreadedDetach(frysk.util.TestFStack)junit.framework.AssertionFailedError: Task #541 #0 0xc5a402 in __kernel_vsyscall () #1 0x0 in null () #2 0x804924a in ../../frysk/frysk-core/frysk/pkglibexecdir/funit-child.c server (): line #249 #3 0x8049c9e in ../../frysk/frysk-core/frysk/pkglibexecdir/funit-child.c main (): line #505 #4 0x0 in null () #5 0x8048d21 in _start () ... did not match: (Task #\d+\n#0 0x[\da-f]+ in __kernel_vsyscall \(\)\n#1 0x[\da-f]+ in (__)?sigsuspend \(\)\n#2 0x[\da-f]+ in ../../frysk/frysk-core/
(testStressMultiThreadedDetach): Note broken - 3691.
Fixed 2006-12-11 frysk-core/frysk/util/CL * TestFStack.java: Stripped down regex's to just the common text between threads. (testClone): Re-enabled (testStressMultiThreadedDetach): Ditto.
Sorry but those 0x0 entries look incorrect there. What is the advocacy of their presence? Currently libunwind even tries to hide the 0x0 entries for teh `((void (*)(void))0)();' NULL-calling case.
Created bug #3863 for issues with what was previously random 0x0 null() bugs and is now 0x.... [unknown] *** This bug has been marked as a duplicate of 3863 ***