[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Libunwind-devel] Testing time
From: |
Ken Werner |
Subject: |
Re: [Libunwind-devel] Testing time |
Date: |
Mon, 28 Mar 2011 16:29:51 +0200 |
User-agent: |
KMail/1.13.5 (Linux/2.6.35-28-generic-pae; KDE/4.5.1; i686; ; ) |
On Friday, March 25, 2011 11:37:19 pm Arun Sharma wrote:
> Hello All,
>
> I went ahead and applied a bunch of patches yesterday. I believe it
> covers most of the things that were discussed on the list recently. I
> still haven't had a chance to review Lassi's performance fixes patch.
> Both 32 and 64 bit x86 are looking good (the same 4 known failures).
>
> Please pull, test and let me know if I broke your platform.
Hi,
Libunwind builds fine on ARMv7-linux-gnueabi when _FORTIFY_SOURCE is
undefinded. The compiler in use is Ubuntu's GCC 4.5.2 (Natty). It seems that a
lot of test cases are failing on ARM but I haven't had a closer look at the
results yet.
make check CFLAGS="-g" UNW_ARM_UNWIND_METHOD=1
===========================================
FAIL: test-proc-info (unw_step() returned 0 instead of -5)
PASS: test-static-link
PASS: test-strerror
FAIL: Gtest-bt (segfaults)
FAIL: Ltest-bt (segfaults)
FAIL: Gtest-exc (result=0 got_here=1 nerrors=1)
FAIL: Ltest-exc (result=0 got_here=1 nerrors=1)
PASS: Gtest-init
FAIL: Ltest-init (didn't reach beginning of unwind-chain)
PASS: Gtest-concurrent
PASS: Ltest-concurrent
PASS: Gtest-resume-sig
PASS: Ltest-resume-sig
FAIL: Gtest-dyn1 (Too many steps to the signal frame (22))
FAIL: Ltest-dyn1 (Too many steps to the signal frame (22))
FAIL: Gtest-trace (segfaults)
FAIL: Ltest-trace (segfaults)
FAIL: test-async-sig (deadlocks)
FAIL: test-flush-cache (segfaults)
PASS: test-init-remote
PASS: test-mem
FAIL: test-setjmp (hangs)
FAIL: test-ptrace (FAILURE: detected 7 errors)
PASS: Ltest-nomalloc
FAIL: rs-race (segfaults)
FAIL: run-check-namespace (Detected 4 errors)
FAIL: run-ptrace-mapper (hangs)
FAIL: run-ptrace-misc (hangs)
===========================================
18 of 28 tests failed
make check CFLAGS="-funwind-tables" UNW_ARM_UNWIND_METHOD=4
===========================================
FAIL: test-proc-info (First call to unw_step() returned 0 instead of -5)
PASS: test-static-link
PASS: test-strerror
FAIL: Gtest-bt (segfaults)
FAIL: Ltest-bt (segfaults)
FAIL: Gtest-exc (result=0 got_here=1 nerrors=1)
FAIL: Ltest-exc (segfaults)
PASS: Gtest-init
FAIL: Ltest-init (didn't reach beginning of unwind-chain)
PASS: Gtest-concurrent
PASS: Ltest-concurrent
PASS: Gtest-resume-sig (segfaults)
FAIL: Ltest-resume-sig (segfaults)
FAIL: Gtest-dyn1 (expected 13, not 1 frames below signal frame)
FAIL: Ltest-dyn1 (segfaults)
FAIL: Gtest-trace (segfaults)
FAIL: Ltest-trace (segfaults)
FAIL: test-async-sig (segfaults)
FAIL: test-flush-cache (segfaults)
PASS: test-init-remote
PASS: test-mem
FAIL: test-setjmp (hangs)
FAIL: test-ptrace (detected 7 errors)
FAIL: Ltest-nomalloc (segfaults)
FAIL: rs-race (segfaults)
FAIL: run-check-namespace (Detected 4 errors)
FAIL: run-ptrace-mapper (hangs)
FAIL: run-ptrace-misc (hangs)
===========================================
20 of 28 tests failed
Regards
Ken
Re: [Libunwind-devel] Testing time,
Ken Werner <=
Re: [Libunwind-devel] Testing time, Lassi Tuura, 2011/03/29
Re: [Libunwind-devel] Testing time, Lassi Tuura, 2011/03/29