From: Vladimir T. <vtz...@gm...> - 2009-10-06 06:54:29
|
On 10/5/09, Don Cohen <don...@is...> wrote: > Vladimir Tzankov writes: > > I guess the problem is the same or related to this one: > > http://thread.gmane.org/gmane.lisp.clisp.devel/20732/ > > > > Currently I cannot reproduce it but I remember that when inspecting > > the C stack there was extra value pushed when vectorof was called. > > I'm willing to do experiments but you'll have to describe in some > detail what you want me to try. Thanks. Let's see whether it is the same problem as reported above. In order to do so you should change the Makefile to keep base/ folder in case of errors - remove "$(RMRF) base" from base target. After you make (and it fails) there should be base/ folder. Now you can run the whole thing under gdb (with all parameters as from make) and see where the segfault happens - please paste stack trace here. Something like (in your build directory): vtz@u32:~/clisp/m$ gdb base/lisp.run (gdb) set args -B . -M base/lispinit.mem -norc -q -i i18n/i18n -i syscalls/posix -i regexp/regexp -i readline/readline (gdb) delete (gdb) handle SIGSEGV nostop noprint (gdb) break spvw_sigsegv.d:65 (gdb) run It should stop at spvw_sigsegv.d:65 - hope the stack is not corrupted. You may try the same thing but removing some of the modules from command line (-i options). Vladimir |