From: Daniel Barlow <dan@te...> - 2001-05-30 17:38:08
I think we may be suffering from libc breakage. Since I upgraded to
the latest debian unstable my previously compiled sbcl binaries are
failing run-program.test.sh with a segmentation fault; it appears to
be related to the alien variable sb-impl::envirion
* (in-package :sb-impl)
* (c-strings->string-list environ)
... but ...
debugger invoked on condition of type SIMPLE-ERROR:
segmentation violation at #X10453F6
0] frame 6
(C-STRINGS->STRING-LIST #<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #X40128648>)
#<SB-ALIEN-INTERNALS:ALIEN-VALUE :SAP #XBFFFFB88>
whatever is being passed to C-STRINGS->STRING-LIST is not the same
thing as SB-IMPL:POSIX-ENVIRON
Rerunning make-target-2.sh fixes it. Anyone (Peter?) want to work out
how we can make binaries that don't break this way? My guess would be
that (def-alien-variable "thing from a shared library") shouldn't be
allowed into code that's going to be dumped into a new core.
http://ww.telent.net/cliki/ - Link farm for free CL-on-Unix resources
From: Peter Van Eynde <pvaneynd@de...> - 2001-05-31 04:15:48
On Wed, May 30, 2001 at 06:06:31PM +0100, Daniel Barlow wrote:
> I think we may be suffering from libc breakage. Since I upgraded to
Note: I just got very strange glibc problems with the lazy images:
EFAULTS (memory bad). The strange thing is that this happens with 'stat'
and that the bad memory is allocated with mallloc!
It's logic Jim, but not as we know it. | pvaneynd@...
"God, root, what is difference?" - Pitr|
"God is more forgiving." - Dave Aronson| http://cvs2.cons.org/~pvaneynd/