Re: [Libunwind-devel] x86_64 system: make check: 6 of 25 tests faile

[Paul Pluzhnikov]

On Mon, Nov 29, 2010 at 7:39 PM, Adam G <address@hidden> wrote:
> Was using RHEL 5, 64-bit.  Really just installing libunwind b/c I need
> Google Perf tools.  Does anyone know how to compile libunwind successfully
> on 64-bit systems?

You appear to have compiled it successfully already :-)

6 failures is what we get elsewhere as well.

Please note, that if you are planning to use tcmalloc on
multi-threaded code, and you call dlopen (or anything that calls
dlopen, e.g. any NSS routines) after some threads are already running,
then libunwind is likely not your friend (you will likely see
deadlocks in dl_iterate_phdr).


> PASS: test-proc-info
> PASS: test-static-link
> PASS: test-strerror
> PASS: Gtest-bt
> PASS: Ltest-bt
> PASS: Gtest-exc
> PASS: Ltest-exc
> PASS: Gtest-init
> PASS: Ltest-init
> PASS: Gtest-concurrent
> PASS: Ltest-concurrent
> failed to get SIGUSR2
> FAILURE: detected 1 errors
> FAIL: Gtest-resume-sig
> failed to get SIGUSR2
> FAILURE: detected 1 errors
> FAIL: Ltest-resume-sig
> FAILURE: expected 13, not 1 frames below signal frame
> FAIL: Gtest-dyn1
> FAILURE: expected 13, not 1 frames below signal frame
> FAIL: Ltest-dyn1
> PASS: test-async-sig
> PASS: test-flush-cache
> PASS: test-init-remote
> PASS: test-mem
> /bin/sh: line 4: 28571 Segmentation fault      ${dir}$tst
> FAIL: test-setjmp
> PASS: test-ptrace
> PASS: Ltest-nomalloc
> PASS: run-check-namespace
> PASS: run-ptrace-mapper
> FAILURE: unw_step() returned -8 for ip=3708e094fc (start ip=3708e094fc)
> unwind failed with ret=-8
> FAILURE: detected 2 errors
> FAIL: run-ptrace-misc
> ===========================================
> 6 of 25 tests failed
> Please report to address@hidden
> ===========================================
>
>
> _______________________________________________
> Libunwind-devel mailing list
> address@hidden
> http://lists.nongnu.org/mailman/listinfo/libunwind-devel
>
>



-- 
Paul Pluzhnikov