[slim-vim] Problems with vim+ecl

Larry Clapp larry at theclapp.org
Sun Apr 2 11:43:34 CDT 2006


On Fri, Mar 31, 2006 at 07:57:27PM +0200, Daniel Trstenjak wrote:
> I have problems with vim+ecl. I just need to call ":ecl" with any
> arguments to get an abort from ecl with the following message:
> 
> "Unrecoverable error:
>  Lisp initialization error."
> 
> Here is the backtrace when calling ":ecl (print "ok")" :
> 
> #0  0xffffe410 in ?? ()
> #1  0xbfffe628 in ?? ()
> #2  0x00000006 in ?? ()
> #3  0x00001cbc in ?? ()
> #4  0x406872c1 in raise () from /lib/tls/libc.so.6
> #5  0x40688b75 in abort () from /lib/tls/libc.so.6
> #6  0x405edaa5 in error (s=0x4062eafd "\nLisp initialization error.\n") at error.d:48
> #7  0x405edae8 in universal_error_handler (narg=3, c=0x8196d00, err=0x819be48, args=0x83b3fb0) at error.d:221
> #8  0x4060b277 in APPLY (n=3, fn=0x405edab0 <universal_error_handler>, x=0x833d014) at apply.d:26
> #9  0x405d5890 in cl_funcall (narg=3, function=0x819d7c8) at eval.d:213
> #10 0x405ed6d7 in cl_error (narg=5, eformat=0x819be48) at error.d:294
> #11 0x405ed8e6 in FEwrong_type_argument (type=0x819aea0, value=0x8337040) at error.d:151
> #12 0x405f06f8 in FEtype_error_real (x=0x8337040) at typespec.d:37
> #13 0x405f258e in make_complex (r=0x8337040, i=0x83a9460) at number.d:228
> #14 0x405e8b9c in sharp_C_reader (in=0x8306910, c=0x10e, d=0x8196d00) at read.d:674
> #15 0x4060ca6b in APPLY_fixed (n=3, fn=0x405e8a80 <sharp_C_reader>, x=0x833d008) at apply.d:677
> #16 0x405d583d in cl_funcall (narg=3, function=0x83352a0) at eval.d:210
> #17 0x405e572e in dispatch_reader_fun (in=0x8306910, dc=0x8e) at read.d:612
> #18 0x4060ca6b in APPLY_fixed (n=2, fn=0x405e5660 <dispatch_reader_fun>, x=0x833d000) at apply.d:677
> #19 0x405d583d in cl_funcall (narg=2, function=0x8335378) at eval.d:210
> #20 0x405e70da in read_object_with_delimiter (in=0x8306910, delimiter=-1) at read.d:118
> #21 0x405e8210 in read_VV (block=0x8321cc0, entry_point=0x4057a608 <init_ECL_NUMLIB>) at read.d:1992
> #22 0x40559f19 in init_LSP (cblock=0x1) at /home/dan.t/downloads/ecl-0.9h/build/ECLINITtk8n70.c:99
> #23 0x405e7f60 in read_VV (block=0x8321fc0, entry_point=0x40559d90 <init_LSP>) at read.d:2007
> #24 0x40559638 in cl_boot (argc=0, argv=0x6) at main.d:459
> #25 0x08160e0e in RunEclCommand (eap=0xbfffec60, cmd=0x81be6b4 "(print \"ok\")") at if_ecl.c:474
> #26 0x08161144 in ex_ecl (eap=0xbfffec60) at if_ecl.c:560
> #27 0x0808b42c in do_one_cmd (cmdlinep=0xbfffeff8, sourcing=0, cstack=0xbfffedd0, 
>     getline=0x809b180 <getexline>, cookie=0x0) at ex_docmd.c:2475
> #28 0x080891b8 in do_cmdline (cmdline=0x0, getline=0x809b180 <getexline>, cookie=0x0, flags=0)
>     at ex_docmd.c:991
> #29 0x080ecc16 in nv_colon (cap=0xbffff0c0) at normal.c:4764
> #30 0x080e70e6 in normal_cmd (oap=0xbffff130, toplevel=1) at normal.c:1116
> #31 0x080b9bb2 in main_loop (cmdwin=0) at main.c:2183
> #32 0x080b984d in main (argc=0, argv=0xbffff378) at main.c:2001
> 
> I have ecl 0.9h, which works well. So I think it seems to be a ecl
> initialization problem.
> 
> I'm using the vim+ecl sources from
> http://69.61.72.246/~dgym/vim+async+ecl.
> 
> My build system is Suse Linux 9.3 with gcc 3.3.5.

1) How do you configure ECL, and how do you configure Vim?

My ECL: 
  ./configure --with-tcp --with-clx --with-x
My Vim: 
  export CFLAGS="-I/usr/local/lib/ecl/ecl"
  ./configure --prefix=/usr --with-x --enable-gui=gtk2 --enable-eclinterp

I use Debian GNU/Linux stable/testing, kernel 2.6.15, gcc 3.3.5.

2) I noticed in the backtrace "... in init_LSP (cblock=0x1) at ...
ECLINITtk8n70.c:99" 
       ^^^

Maybe disable Tk in ECL?  Just a guess.

(FYI, I use CVS ECL from circa March 10, which is why I need the
CFLAGS for my Vim configure, 'cause Jim uses stock ECL 0.9h, which has
a different include path.)

BTW (showing my C ignorance here) how'd you get a backtrace?

-- L



More information about the slim-vim mailing list