Re: [Libunwind-devel] Testing time

[Arun Sharma]

On Fri, Mar 25, 2011 at 4:28 PM, Joe Damato <address@hidden> wrote:
>> Should -U_FORTIFY_SOURCE be on by default for libunwind builds?
>
> no this is an ubuntu security feature so the deb packager would just
> do this in the debian/rules file, imo.
>

Yeah - this is probably best left to distro packagers.

Paul, the 4 failures I see on Ubuntu are:

FAILURE: expected 13, not 12 frames below signal frame
FAIL: Gtest-dyn1
FAILURE: expected 13, not 12 frames below signal frame
FAIL: Ltest-dyn1
/bin/bash: line 5: 22628 Segmentation fault      ${dir}$tst
FAIL: test-setjmp
FAILURE: unw_step() returned -8 for ip=2b566374879e (start ip=2b566374879e)
unwind failed with ret=-8
FAILURE: detected 2 errors
FAIL: run-ptrace-misc

On a recent chroot from:

http://ftp.osuosl.org/pub/funtoo/funtoo-current/x86-64bit/core2_64/

Using:

https://github.com/adsharma/adsharma-overlay/blob/master/sys-libs/libunwind/libunwind-9999.ebuild

I get 3 failures. test-setjmp passes.

 -Arun