[Openmcl-devel] ccl crashes
Mario S. Mommer
m_mommer at yahoo.com
Wed Jan 20 20:46:13 UTC 2010
no, that crashes just the same.
mommer at nick:~/local/src/ccl$ lx86cl64 -n
Welcome to Clozure Common Lisp Version 1.4-r13391M (LinuxX8664)!
? (load "coretest")
? (coretest::start-threads 2 #'coretest::consing-f)
? Segmentation fault
mommer at nick:~/local/src/ccl$
Gail Zacharias <gz at clozure.com> writes:
> Does it work using the -n option, i.e. invoking ccl like this:
> lx86cl64 -n
> On Wed, Jan 20, 2010 at 3:09 PM, Mario S. Mommer <m_mommer at yahoo.com> wrote:
>> "R. Matthew Emerson" <rme at clozure.com> writes:
>>>> anything else to try for obtaining a good backtrace?
>>> See http://trac.clozure.com/ccl/wiki/CclUnderGdb
>>> It's important to source /path/to/ccl/lisp-kernel/linuxx8664/.gdbinit
>>> before running (to tell gdb what signals to pass to the lisp). The
>>> lisp handles SIGSEGV itself all day long.
>>> If you can get it to crash running under gdb, maybe that will help
>>> with getting a little more information.
>> I have the same problem on two rather different machines, but in gdb, it
>> runs flawlessly on both.
>> Openmcl-devel mailing list
>> Openmcl-devel at clozure.com
More information about the Openmcl-devel