[Libunwind-devel] Problems with compiling libunwind on Ubuntu 10.04

[Theodore Ts'o]

Hi there,

I'm wondering if people have run into problems compiling libunwind on
Ubuntu 10.04.

The first problem I ran into was caused by an incompatibility with the
longjmp implementation and Fortify.  By passing
"CFLAGS=-D_FORTIFY_SOURCE=0" to configure, I was able to get libunwind to
compile.  However, it then failed the "make check":

Making check in src
make[1]: Entering directory `/kbuild/libgoogle/libunwind/src'
make  check-am
make[2]: Entering directory `/kbuild/libgoogle/libunwind/src'
make[2]: Nothing to be done for `check-am'.
make[2]: Leaving directory `/kbuild/libgoogle/libunwind/src'
make[1]: Leaving directory `/kbuild/libgoogle/libunwind/src'
Making check in tests
make[1]: Entering directory `/kbuild/libgoogle/libunwind/tests'
make  test-proc-info test-static-link test-strerror Gtest-bt Ltest-bt Gtest-exc 
Ltest-exc Gtest-init Ltest-init Gtest-concurrent Ltest-concurrent 
Gtest-resume-sig Ltest-resume-sig Gtest-dyn1 Ltest-dyn1 Gtest-trace Ltest-trace 
test-async-sig test-flush-cache test-init-remote test-mem test-setjmp 
test-ptrace Ltest-nomalloc Ltest-nocalloc rs-race   run-check-namespace 
run-ptrace-mapper run-ptrace-misc 
make[2]: Entering directory `/kbuild/libgoogle/libunwind/tests'
make[2]: `test-proc-info' is up to date.
make[2]: `test-static-link' is up to date.
make[2]: `test-strerror' is up to date.
make[2]: `Gtest-bt' is up to date.
make[2]: `Ltest-bt' is up to date.
make[2]: `Gtest-exc' is up to date.
make[2]: `Ltest-exc' is up to date.
make[2]: `Gtest-init' is up to date.
make[2]: `Ltest-init' is up to date.
make[2]: `Gtest-concurrent' is up to date.
make[2]: `Ltest-concurrent' is up to date.
make[2]: `Gtest-resume-sig' is up to date.
make[2]: `Ltest-resume-sig' is up to date.
make[2]: `Gtest-dyn1' is up to date.
make[2]: `Ltest-dyn1' is up to date.
make[2]: `Gtest-trace' is up to date.
make[2]: `Ltest-trace' is up to date.
make[2]: `test-async-sig' is up to date.
make[2]: `test-flush-cache' is up to date.
make[2]: `test-init-remote' is up to date.
make[2]: `test-mem' is up to date.
make[2]: `test-setjmp' is up to date.
make[2]: `test-ptrace' is up to date.
make[2]: `Ltest-nomalloc' is up to date.
make[2]: `Ltest-nocalloc' is up to date.
make[2]: `rs-race' is up to date.
make[2]: Nothing to be done for `run-check-namespace'.
make[2]: Nothing to be done for `run-ptrace-mapper'.
make[2]: Nothing to be done for `run-ptrace-misc'.
make[2]: Leaving directory `/kbuild/libgoogle/libunwind/tests'
make  check-TESTS
make[2]: Entering directory `/kbuild/libgoogle/libunwind/tests'
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
PASS: Gtest-resume-sig
PASS: Ltest-resume-sig
FAILURE: expected 13, not 12 frames below signal frame
FAIL: Gtest-dyn1
FAILURE: expected 13, not 12 frames below signal frame
FAIL: Ltest-dyn1
PASS: Gtest-trace
PASS: Ltest-trace
PASS: test-async-sig
PASS: test-flush-cache
PASS: test-init-remote
PASS: test-mem
/bin/sh: line 5: 27059 Segmentation fault      ${dir}$tst
FAIL: test-setjmp
PASS: test-ptrace
PASS: Ltest-nomalloc
FAILURE: detected 1 error (malloc: 0, calloc: 1)
FAIL: Ltest-nocalloc
PASS: rs-race
PASS: run-check-namespace
PASS: run-ptrace-mapper
FAILURE: unw_step() returned -8 for ip=2b961a2e379e (start ip=2b961a2e379e)
unwind failed with ret=-8
FAILURE: detected 2 errors
FAIL: run-ptrace-misc
===========================================
5 of 29 tests failed
Please report to address@hidden
===========================================
make[2]: *** [check-TESTS] Error 1
make[2]: Leaving directory `/kbuild/libgoogle/libunwind/tests'
make[1]: *** [check-am] Error 2
make[1]: Leaving directory `/kbuild/libgoogle/libunwind/tests'
make: *** [check-recursive] Error 1

Does this ring a bell?  Is there anything I should try?  This is with
the latest git checkout of libunwind.

Thanks,

                                                - Ted