[Ecls-list] clx segmentation violation

[Julian Stecklina]

Hello,

running ECL built from Git on my Gentoo x86 box yesterday with

./configure --prefix=$HOME/local-install --with-clx

I get a segmentation violation when doing (require :clx). GDB session
follows:

(gdb) r -norc
Starting program: /home/julian/local-install/bin/ecl -norc
[Thread debugging using libthread_db enabled]
[New Thread 0xb7ca1b00 (LWP 8927)]
ECL (Embeddable Common-Lisp) 0.9j (CVS 2008-05-22 13:14)
Copyright (C) 1984 Taiichi Yuasa and Masami Hagiya
Copyright (C) 1993 Giuseppe Attardi
Copyright (C) 2000 Juan J. Garcia-Ripoll
ECL is free software, and you are welcome to redistribute it
under certain conditions; see file 'Copyright' for details.
Type :h for Help.  Top level.
> (require :clx)
;;; Loading #P"/home/julian/local-install/lib/ecl/clx.fas"

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb7ca1b00 (LWP 8927)]
0xb7f76cd0 in do_patch_sharp (x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/build/ecl/object.h:753
753		return (i? (cl_type)i : (cl_type)(o->d.t));
(gdb) bt
#0  0xb7f76cd0 in do_patch_sharp (x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/build/ecl/object.h:753
#1  0xb7f76dd4 in do_patch_sharp (x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/read.d:1174
#2  0xb7f76ed1 in patch_sharp (x=0x82e78e8) at /home/julian/src/lisp-implementations/ecl/src/c/read.d:1210
#3  0xb7f7b339 in read_VV (block=0x82714e0, entry_point=0xb7c4c260 <_ecliqKz4_Vo7Vj3>) at /home/julian/src/lisp-implementations/ecl/src/c/read.d:2120
#4  0xb7b70f12 in init_fas_CODE (cblock=0x3) at /home/julian/src/lisp-implementations/ecl/build/ECLINITjrbkEn.c:77
#5  0xb7f7b36e in read_VV (block=0x812c660, entry_point=0xb7b70cc0 <init_fas_CODE>) at /home/julian/src/lisp-implementations/ecl/src/c/read.d:2129
#6  0xb7f9bea8 in si_load_binary (filename=0x82dcce0, verbose=0xb7fd8098, print=0x1) at /home/julian/src/lisp-implementations/ecl/src/c/load.d:364
#7  0xb7faae77 in APPLY_fixed (n=3, fn=0x100, x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/apply.d:678
#8  0xb7f65f08 in ecl_apply_from_stack_frame (frame=0xbfffea58, x=0xb7fe0828) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:75
#9  0xb7f65fbb in cl_funcall (narg=4, function=0xb7fe0828) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:199
#10 0xb7f9c43c in cl_load (narg=3, source=0x82dcd00) at /home/julian/src/lisp-implementations/ecl/src/c/load.d:494
#11 0xb7f23be2 in LC3__g16756 (V1=0x82c4678) at /home/julian/src/lisp-implementations/ecl/build/lsp/module.c:144
#12 0xb7faae49 in APPLY_fixed (n=1, fn=0x100, x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/apply.d:676
#13 0xb7f65f08 in ecl_apply_from_stack_frame (frame=0xbfffecb8, x=0x81b67d0) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:75
#14 0xb7f65fbb in cl_funcall (narg=2, function=0x81b67d0) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:199
#15 0xb7f24036 in LC2__g16754 (narg=1, env0=0x82dff20, V1=0x81b67d0) at /home/julian/src/lisp-implementations/ecl/build/lsp/module.c:116
#16 0xb7fa664e in APPLY_closure (n=256, fn=0xb7f23ffc <LC2__g16754>, cl=0x82dff20, x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/apply.d:351
#17 0xb7f65ed9 in ecl_apply_from_stack_frame (frame=0xbfffee70, x=0x82dff00) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:80
#18 0xb7f66212 in cl_apply (narg=2, fun=0x82dff00, lastarg=0x1) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:230
#19 0xb7ed748e in cl_some (narg=2, V1=0x82dff00, V2=0x81b67c0) at /home/julian/src/lisp-implementations/ecl/build/lsp/seq.c:671
#20 0xb7f23f8b in cl_require (narg=1, V1=0x82c4678) at /home/julian/src/lisp-implementations/ecl/build/lsp/module.c:96
#21 0xb7fa1d1b in APPLY (n=256, fn=0xb7f23d1a <cl_require>, x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/apply.d:26
#22 0xb7f65f67 in ecl_apply_from_stack_frame (frame=0xbffff0ac, x=0xb7fdc3a0) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:78
#23 0xb7f66652 in interpret_funcall (narg=<value optimized out>, fun=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/interpreter.d:490
#24 0xb7f67212 in ecl_interpret (bytecodes=0x82ab6f0, pc=0x8283ab0) at /home/julian/src/lisp-implementations/ecl/src/c/interpreter.d:718
#25 0xb7f6b1dd in si_eval_with_env (narg=2, form=0x82dff90) at /home/julian/src/lisp-implementations/ecl/src/c/compiler.d:2586
#26 0xb7f29182 in L3tpl (narg=0) at /home/julian/src/lisp-implementations/ecl/build/lsp/top.c:149
#27 0xb7f29c60 in L1top_level () at /home/julian/src/lisp-implementations/ecl/build/lsp/top.c:40
#28 0xb7faae3f in APPLY_fixed (n=0, fn=0x100, x=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/apply.d:675
#29 0xb7f65f08 in ecl_apply_from_stack_frame (frame=0xbffff42c, x=0xb7fdeb48) at /home/julian/src/lisp-implementations/ecl/src/c/eval.d:75
#30 0xb7f66652 in interpret_funcall (narg=<value optimized out>, fun=0xc0408000) at /home/julian/src/lisp-implementations/ecl/src/c/interpreter.d:490
#31 0xb7f67212 in ecl_interpret (bytecodes=0x82ab720, pc=0x81a5cc8) at /home/julian/src/lisp-implementations/ecl/src/c/interpreter.d:718
#32 0xb7f6b1dd in si_eval_with_env (narg=2, form=0x82d9740) at /home/julian/src/lisp-implementations/ecl/src/c/compiler.d:2586
#33 0xb7f28b20 in si_safe_eval (narg=3, V1=0x82d9740, V2=0x1, V3=0x0) at /home/julian/src/lisp-implementations/ecl/build/lsp/top.c:2051
#34 0x080487ae in main (argc=Cannot access memory at address 0x100
) at /home/julian/src/lisp-implementations/ecl/build/ECLINITkvZDZE.c:55

Regards,
-- 
Julian Stecklina

Well, take it from an old hand: the only reason it would be easier to
program in C is that you can't easily express complex problems in C,
so you don't. - Erik Naggum (in comp.lang.lisp)

(Spam-Experiment: http://cthulhu.c3d2.de/~astro/badpit.html )