Your message dated Fri, 22 Sep 2017 10:13:32 +0200
with message-id <1506068012.12056.20.ca...@debian.org>
and subject line Re: Bug#752726: stumpwm: FTBFS - SIGSEGV cannot be cured.
has caused the Debian Bug report #752726,
regarding stumpwm: FTBFS - SIGSEGV cannot be cured.
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 ow...@bugs.debian.org
immediately.)
--
752726: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=752726
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: stumpwm
Version: 2:0.9.8-1
Severity: serious
Usertags: goto-cc
During a rebuild of all Debian packages in a clean sid chroot (using cowbuilder
and pbuilder) the build failed with the following error.
[...]
;; Compiling file
/srv/jenkins-slave/workspace/sid-goto-cc-stumpwm/stumpwm-0.9.8/workarounds.lisp
...
WARNING: INTERN("FIRST-ZERO"): #<PACKAGE XLIB> is locked
Ignore the lock and proceed
WARNING: INTERN("SECOND-ZERO"): #<PACKAGE XLIB> is locked
Ignore the lock and proceed
WARNING: INTERN("SAVED"): #<PACKAGE XLIB> is locked
Ignore the lock and proceed
*** - handle_fault error2 ! address = 0x55434f462d6c not in
[0xccce8f690,0xccd0ce000) !
SIGSEGV cannot be cured. Fault address = 0x55434f462d6c.
GC count: 322
Space collected by GC: 553724984
Run time: 28 145758
Real time: 28 859593
GC time: 4 188248
Permanently allocated: 187488 bytes.
Currently in use: 7931696 bytes.
Free space: 1618612 bytes.
Segmentation fault
Makefile:40: recipe for target 'stumpwm.texi' failed
I'm not sure whether this is a clisp bug or a problem in stumpwm; the full build
log is attached, but please do let me know if the error turns out to be
unreproducible.
Best,
Michael
stumpwm-build-log.txt.gz
Description: application/gunzip
pgpkBxIYOWuil.pgp
Description: PGP signature
--- End Message ---
--- Begin Message ---
On Fri, 30 Jan 2015 16:05:28 +0100 Agustin Martin <agmar...@debian.org> wrote:
> On Sun, Dec 21, 2014 at 08:11:24PM +0100, Thomas Vincent wrote:
> > Hello,
> >
> > Damien 'drazzib' Raude-Morvan and I tried to reproduce this bug in
> > chroots (with sbuild) in both jessie and sid:
> >
> > * using the current stumpwm package from sid and setting clisp as the
> > compiler
> > * creating a complete chroot from snapshot.debian.org (20140625)
> > corresponding to the date this bug report was filled
> >
> > We were in each case unable to reproduce this bug both about the build
> > and the command given in message #21.
>
> I also tried unsuccessfully to reproduce this problem with procedure
> described in #21 by Michael. Using an amd64 sid chroot and stumpwm
> modified to use clisp for build and run, no luck.
>
> Also, it must be noted that stumpwm has switched from clisp to sbcl in
> stumpwm:2:0.9.8-7, already in testing. For this reason this problem
> no longer affects stumpwm for jessie.
Closing, since the problem is unreproducible and no longer affects
stumpwm (which has moved away from clisp).
--
⢀⣴⠾⠻⢶⣦⠀ Sébastien Villemot
⣾⠁⢠⠒⠀⣿⡁ Debian Developer
⢿⡄⠘⠷⠚⠋⠀ http://sebastien.villemot.name
⠈⠳⣄⠀⠀⠀⠀ http://www.debian.org
signature.asc
Description: This is a digitally signed message part
--- End Message ---
_______________________________________________
pkg-common-lisp-devel mailing list
pkg-common-lisp-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-common-lisp-devel
