> > After upgrading to 2.7-9 of libc6 in unstable, SBCL became extremely > > prone to crashing > > randomly (i.e. 5-10 source files compiled of the SBCL CVS code before a > > 100% CPU hang which > > was only killable with -s 9. > > Could you please give a way to reproduce the bug? I know nothing about > SBCL, so a list of commands to execute or a shell script would be nice. Of course, sorry. Probably the easiest option is to get sbcl and darcs (the version control system). It doesn't appear to matter which version of sbcl - I've had the problem with 1.0.12 up to 1.0.14. Then get clbuild (which is a little shell script which can among other things get and build a new copy of sbcl, which is a project large enough to guarantee the hang on my computer at least) using darcs get http://common-lisp.net/project/clbuild/clbuild Chmod +x the clbuild script inside the folder and cd inside and run ./clbuild buildsbcl Hopefully (!) your system should hang at 100% CPU with the sbcl process ignoring SIGTERM. Sorry about the involved duplication process - it's just that you need to compile quite a bit of code before the seemingly "random" bug strikes. > Could you please try to narrow the problem to a single libc6 version? > Older versions are available on snapshot.debian.net. > Could you let me know a way to convince dpkg to let me do that? Since you have to up/downgrade a dependent package at the same time, and I'm a bit scared of using --force-all on libc6 on my only computer! (Or am I being needlessly cautious?) Incidentally, as someone pointed out in the sbcl thread I linked to, it's quite possible that your change in libc6 has thrown up a bug in sbcl rather than the other way round - we're trying (and failing) to get strace,gdb to tell us something useful about where sbcl died. However, I'd be extremely grateful if you could suggest what change you think is likely to be able to cause this sort of symptom - and I stand by my categorization: the change definitely breaks an unrelated package :P Thanks for the really prompt response! Rupert
Attachment:
signature.asc
Description: This is a digitally signed message part