8) testClone(frysk.util.TestFStack)junit.framework.AssertionFailedError: Task #23053
#0 0x3a3402 in __kernel_vsyscall ()
#1 0xca2966 in nanosleep ()
#2 0xca278b in sleep ()
#3 0x8048d5d in ../../frysk/frysk-core/frysk/pkglibdir/funit-threads.c main ():
#4 0xc2d4e4 in __libc_start_main ()
#5 0x8048801 in _start ()
did not match: (Task #\d+\n#0 0x[\da-f]+ in __kernel_vsyscall \(\)\n#1
0x[\da-f]+ in __nanosleep_nocancel \(\)\n#2 0x[\da-f]+ in sleep
note the nanosleep vs __nanosleep_nocancel.
For FStack it might be better to focus on the UI interface, and the broad format
of the output, and not be too worried about the exacting details of the stack
backtrace. Assume here that libunwind and its bindings have unit tests covering
Of course, if those lack coverage then the thing to do is expand those tests at
2006-12-10 Andrew Cagney <email@example.com>
* TestFStack.java (testCloen): Note broken - 3690.
* TestFStack.java: Stripped down regex's to just the common text between threads.
Please provide the `Value' and `Size' fields of `readelf -a libc.so.6' of the
symbols involved, therefore `nanosleep' and `__nanosleep_nocancel'. They look as
overlapping while I was improving the related libunwind resolving functionality
it would be good to know if there really isn't some bug.
Two bugs here; TestJUnit was to pedantic; a potential problem with libunwind.
Nurdin, can you create a new libunwind bug, blocking this, and fill in as much
information as possible.
Closing, 3702 deals with the libunwind problem.