Re: [Sbcl-devel] SBCL hanging seemingly randomly

[Dietrich B. <di...@we...>]

Hi,

I have the same problem: sbcl hangs randomly almost every time
when I try to compile my code.

As in the other cases reported the cpu runs at 100% and sbcl can only
be killed with a KILL signal.

I am using debian sid on a vanilla kernel patched for realtime and
experienced this problem for the first time yesterday.

I installed sbcl using `clbuild' and not from the debian packages -
ironically in order to avoid a 100% busy cpu when trying to use mcclim
with cmucl.

I had the impression that things get worse when trying to compile from
emacs/slime and the only strategy which somehow gives me the
possibility to continue with my work is to compile my sources
asdf-system by asdf-system from the shell and to load the compiled
sources from slime after.  This strategy only works from time to time
though.

I also had the impression that this might be caused by the
sbcl-threads - but this is just a feeling in my case :)

You mentioned that the problems vanished after downgrading libc6 to
version 2.7-6 - Is there an easy way to use a downgraded libc6 version
only for sbcl until the problem (if this really is the reason) is
solved?

Thanks for your help!

Dietrich


Here the output of gdb:

------------------------------------------------------------
dietrich@pippi:~ $ gdb -p 25549
GNU gdb 6.7.1-debian
Copyright (C) 2007 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show
copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
Attaching to process 25549
/build/buildd/gdb-6.7.1/gdb/linux-nat.c:979: internal-error:
linux_nat_attach: Assertion `pid == GET_PID (inferior_ptid) &&
WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

/build/buildd/gdb-6.7.1/gdb/linux-nat.c:979: internal-error:
linux_nat_attach: Assertion `pid == GET_PID (inferior_ptid) &&
WIFSTOPPED (status) && WSTOPSIG (status) == SIGSTOP' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Create a core file of GDB? (y or n) n
A program is being debugged already.  Kill it? (y or n) n
Program not killed.
(gdb) call backtrace_from_fp($ebp, 100)
No symbol table is loaded.  Use the "file" command.
(gdb) q
The program is running.  Quit anyway (and detach it)? (y or n) y
Detaching from program: , process 25549
dietrich@pippi:~ $ pkill -9 sbcl
------------------------------------------------------------

and here the strace piped to head:
------------------------------------------------------------
dietrich@pippi:~ $ strace -p 27131 2>&1 | head
Process 27131 attached - interrupt to quit
--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
--- SIGSTOP (Stopped (signal)) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
dietrich@pippi:~ $ pkill -9 sbcl
------------------------------------------------------------