[Ecls-list] Problems with ECL in vim

Juan Jose Garcia Ripoll lisp at arrakis.es
Tue Apr 4 01:24:03 UTC 2006

On Mon, 2006-04-03 at 21:43 +0200, Daniel Trstenjak wrote:
> One thing they have alreay done is embedding ECL in vim.
> It seems to work for all project members. 
> Unfortunately it does not work for me, and nobody
> of the project has a clue why.

Do you use the same version? CVS or one of the latest tarballs?

> Here is the backtrace when calling (print "ok"):
> #4  0x406a42c1 in raise () from /lib/tls/libc.so.6
> #5  0x406a5b75 in abort () from /lib/tls/libc.so.6
> #6  0x405f02e5 in error (s=0x4063c795 "\nLisp initialization error.\n") at error.d:48
> #7  0x405f0328 in universal_error_handler (narg=3, c=0x81961a0, err=0x819b300, args=0x83b0f80) at error.d:221
> #8  0x4060df97 in APPLY (n=3, fn=0x405f02f0 <universal_error_handler>, x=0x833b014) at apply.d:26
> #9  0x405d8122 in cl_funcall (narg=3, function=0x819cc38) at eval.d:219
> #10 0x405eff17 in cl_error (narg=5, eformat=0x819b300) at error.d:294
> #11 0x405f0126 in FEwrong_type_argument (type=0x819a358, value=0x8335100) at error.d:151
> #12 0x405f2ee8 in FEtype_error_real (x=0x8335100) at typespec.d:36
> #13 0x405f4d6e in make_complex (r=0x8335100, i=0x83a2480) at number.d:231
> #14 0x405eb3dc in sharp_C_reader (in=0x8303910, c=0x10e, d=0x81961a0) at read.d:679
> #15 0x4060f78b in APPLY_fixed (n=3, fn=0x405eb2c0 <sharp_C_reader>, x=0x833b008) at apply.d:677
> #16 0x405d80b1 in cl_funcall (narg=3, function=0x8333b28) at eval.d:216
> #17 0x405e7ebe in dispatch_reader_fun (in=0x8303910, dc=0x8e) at read.d:617
> #18 0x4060f78b in APPLY_fixed (n=2, fn=0x405e7df0 <dispatch_reader_fun>, x=0x833b000) at apply.d:677
> #19 0x405d80b1 in cl_funcall (narg=2, function=0x8333c00) at eval.d:216
> #20 0x405e986a in read_object_with_delimiter (in=0x8303910, delimiter=-1) at read.d:123
> #21 0x405ea970 in read_VV (block=0x830cbd0, entry_point=0x4057f687 <init_ECL_NUMLIB>) at read.d:2001
> #22 0x4055f079 in init_LSP (cblock=0x1) at /home/dan.t/downloads/ecls/build/ECLINITQI7Y8c.c:98
> #23 0x405ea8cb in read_VV (block=0x830cfc0, entry_point=0x4055eef0 <init_LSP>) at read.d:2023
> #24 0x4055e77b in cl_boot (argc=0, argv=0x6) at main.d:451

There seems to be a problem at initialization time. ECL is reading all
constant values used by a module and it fails to read some complex
number. I cannot locate the precise module where this seems to happen,
because inly the reference to init_LSP is left. Inspecting the data
section of that module might help identify whether the data is corrupt.

What I wonder is why cl_boot() was not called before. Does this
interface wait for the first lisp command to initalize ECL? Or is it
accidentally calling cl_boot() a second time?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <https://mailman.common-lisp.net/pipermail/ecl-devel/attachments/20060404/1f8492cf/attachment.sig>

More information about the ecl-devel mailing list