[clisp-list] Re: FFI debugging and crashing support - Thanks

[Surendra S. <ss...@sp...>]

Sam Steingold <sd...@gn...> writes:

>> * Surendra Singhi <rsh...@ar...g> [2005-08-02 21:58:16 -0700]:
>>
>> Sam Steingold <sd...@gn...> writes:
>>
>>>> * Surendra Singhi <rsh...@ar...g> [2005-07-31 00:27:55 -0700]:
>>>>
>>>> Is there any way (flags, tools), which I can use to avoid clisp from
>>>> crashing, also get better error checking and more warnings?
>>>
>>> <http://clisp.cons.org/impnotes/dffi.html#ffi-extern-output>
>>>
> all your DEF-CALL-OUT forms have a (:LIBRARY ...) argument, right?
> comment it out and then re-compile wxToolBar.lisp.
>
Yes, indeed that was the case, commenting and recompiling fixed it.
Thanks once again.

>> [2]when clisp crashes it does not generates any core dump file, is
>> there any way I can get the stack trace or some information on why did
>> it crash or what made it crash, or make it generate a core dump?
>
> running under a debugger (e.g., gdb) should help.
> I don't know how to tell windows to generate core dumps.
> in my experience it does generate "stacktrace" files (smallish ASCII
> files with number that I don't know how to interpret).
>
I will try that.

Regards,
-- 
Surendra Singhi

http://www.spikesource.com

http://www.public.asu.edu/~sksinghi/index.html