$ ./TestRunner lib.dw.tests.TestDwfl Running testGetLine(lib.dw.tests.TestDwfl) ...FAIL junit.framework.AssertionFailedError: expected:<51> but was:<52> Running testGetDie(lib.dw.tests.TestDwfl) ...PASS Time: 0.003 There was 1 failure: 1) testGetLine(lib.dw.tests.TestDwfl)junit.framework.AssertionFailedError: expected:<51> but was:<52> at lib.dw.tests.TestDwfl.testGetLine(TestRunner) at frysk.junit.Runner.<init>(TestRunner) at TestRunner.main(TestRunner) FAILURES!!! Tests run: 2, Failures: 1, Errors: 0 This seems to be an off by one error on x86-64
This has now been fixed: 2006-07-31 Adam Jocksch <ajocksch@redhat.com> * tests/TestDwfl.java (testGetLine): Fixed, test now works on x86_64.
On x8664: 1) testGetLine(lib.dw.tests.TestDwfl)junit.framework.AssertionFailedError: expected:<55> but was:<51> at lib.dw.tests.TestDwfl.testGetLine(TestRunner) at frysk.junit.Runner.<init>(TestRunner) at TestRunner.main(TestRunner) Perhaps the line number encoded in the Dwarf depends on the exact version of the system's gcc?
(In reply to comment #2) > On x8664: > 1) testGetLine(lib.dw.tests.TestDwfl)junit.framework.AssertionFailedError: > expected:<55> but was:<51> > at lib.dw.tests.TestDwfl.testGetLine(TestRunner) > at frysk.junit.Runner.<init>(TestRunner) > at TestRunner.main(TestRunner) > > Perhaps the line number encoded in the Dwarf depends on the exact version of the > system's gcc? Hi, Tim, I removed "if (brokenXXX(2965))" to let testGetLine run. This case could pass on our X86-64 box with 2.6.15-1.2054_FC5. [qiyao@YZ_X86_64 ~/build-frysk/frysk-imports]$ ./TestRunner lib.dw.tests.TestDwfl Running testGetLine(lib.dw.tests.TestDwfl) ...PASS Running testGetDie(lib.dw.tests.TestDwfl) ...PASS Time: 0.002 OK (2 tests) [qiyao@YZ_X86_64 ~/build-frysk/frysk-imports]$ gcc -v Using built-in specs. Target: x86_64-redhat-linux Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --infodir=/usr/share/info --enable-shared --enable-threads=posix --enable-checking=release --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-libgcj-multifile --enable-languages=c,c++,objc,obj-c++,java,fortran,ada --enable-java-awt=gtk --disable-dssi --with-java-home=/usr/lib/jvm/java-1.4.2-gcj-1.4.2.0/jre --with-cpu=generic --host=x86_64-redhat-linux Thread model: posix gcc version 4.1.1 20060525 (Red Hat 4.1.1-1)
Also passes for me with current CVS and brokenXXX() removed on: $ uname -a Linux dijkstra.wildebeest.org 2.6.17-1.2174_FC5 #1 SMP Tue Aug 8 15:30:44 EDT 2006 x86_64 x86_64 x86_64 GNU/Linux $ gcc --version gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)
Tim, are you still seeing this?
Hi, Tim, I enabled this test case except on X86_64, 2006-09-19 Yao Qi <qiyaoltc@cn.ibm.com> * TestCase.java (brokenX8664XXX): New method. 2006-09-19 Yao Qi <qiyaoltc@cn.ibm.com> * tests/TestDwfl.java (testGetLine): Skip it when build on X86_64. Change the line number result for powerpc64. If this problem does not exist on your box, please remove brokenX8664XXX in TestDwfl.java to make this case run on all the platforms, and close this bug. Thanks!
Should now work similar on all architectures: 2006-09-19 Mark Wielaard <mark@klomp.org> * tests/cni/TestLib.cxx (getFuncAddr): Extract define out of function and put whole definition on one line. * tests/TestDwfl.java (testGetLine): Use same line number for all architectures.