Bug#544905: marked as done (libsigsegv: FTBFS on amd64: Test failure)
Your message dated Mon, 28 Dec 2009 17:22:12 +0100
with message-id <20091228162212.GA18822@galadriel.inutil.org>
and subject line Re: Bug#544905 closed by Bastian Blank <waldi@debian.org> (Bug#544905: fixed in linux-2.6 2.6.32~rc8-1~experimental.1)
has caused the Debian Bug report #544905,
regarding libsigsegv: FTBFS on amd64: Test failure
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
544905: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=544905
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: libsigsegv: FTBFS on amd64: Test failure
- From: Daniel Schepler <dschepler@gmail.com>
- Date: Thu, 3 Sep 2009 10:43:04 -0700
- Message-id: <200909031043.04230.dschepler@gmail.com>
Package: libsigsegv
Version: 2.5-3
Severity: serious
From my pbuilder build log (on amd64):
...
# Make sure libsigsegv works
/usr/bin/make check
make[1]: Entering directory `/tmp/buildd/libsigsegv-2.5'
Making check in src
make[2]: Entering directory `/tmp/buildd/libsigsegv-2.5/src'
make[2]: Nothing to be done for `check'.
make[2]: Leaving directory `/tmp/buildd/libsigsegv-2.5/src'
Making check in tests
make[2]: Entering directory `/tmp/buildd/libsigsegv-2.5/tests'
/usr/bin/make check-TESTS
make[3]: Entering directory `/tmp/buildd/libsigsegv-2.5/tests'
Test passed.
PASS: sigsegv1
Test passed.
PASS: sigsegv2
Starting recursion pass 1.
Stack overflow 1 caught.
Starting recursion pass 2.
Stack overflow 2 caught.
Test passed.
PASS: stackoverflow1
/bin/sh: line 5: 4730 Segmentation fault ${dir}$tst
FAIL: stackoverflow2
===================
1 of 4 tests failed
===================
make[3]: *** [check-TESTS] Error 1
make[3]: Leaving directory `/tmp/buildd/libsigsegv-2.5/tests'
make[2]: *** [check-am] Error 2
make[2]: Leaving directory `/tmp/buildd/libsigsegv-2.5/tests'
make[1]: *** [check-recursive] Error 1
make[1]: Leaving directory `/tmp/buildd/libsigsegv-2.5'
make: *** [build-stamp] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2
--
Daniel Schepler
--- End Message ---
--- Begin Message ---
Version: 2.6.32-2
On Sun, Dec 06, 2009 at 01:09:58PM +0100, Sebastian Andrzej Siewior wrote:
> * Daniel Schepler | 2009-11-25 11:47:07 [-0800]:
>
> >I just tried building libsigsegv under this version of linux-image-2.6.32-rc8-
> >amd64 and still got the same build failure.
>
> Yes, because the patch never made it into the kernel. The changelog says:
> | [ Ben Hutchings ]
> | * New upstream release candidate.
> | - signal: Fix alternate signal stack check (Closes: #544905)
>
> and this is not the case. I wrote earler [0] that the patch is in the
> TIP tree and _will_ be merged into Linus' tree. I should probably not
> have mention this part in order not cause any confusion what I obviously
> have done.
> However, the patch is now merged into Linus' tree [1] and it will show up
> in v2.6.33-rc1. Due to its stable tag, the patch should pop up v2.6.32.X
> series.
>
> In the meantime libsigsegfault upstream maintainer applied a duck tape
> patch [2] to pass the test which just lame IMHO.
>
> [0] http://bugs.debian.org/cgi-bin/bugreport.cgi?msg=34;att=0;bug=544905
> [1] http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=2a855dd01bc1539111adb7233f587c5c468732ac
> [2] http://git.savannah.gnu.org/cgit/libsigsegv.git/commit/?id=4f14ef87b2fba9718c1a88b9ed9ca7ba111d60da
Sebastian's patch was merged in 2.6.32.1, which ended up in 2.6.32-2.
Cheers,
Moritz
--- End Message ---
Reply to: