Re: [clisp-list] Debugging clisp FFI calls into a newly created (c++) DLL

[Arseny S. <am...@ic...>]

> I wrote a (c++) DLL using msvc 6.0. So far clisp 'call-outs' and 'call-ins' work fine.
> Now - since things get more complex - I'd like to be able to debug my DLL using msvc debugger. This is normally no problem, but when I try to start debugging the clisp process I run into an
> access violation
> exception. I can't start clisp (lisp.exe -M lispinit.mem ...) from within the debugger. If I don't specify the image, I don't run into any access violation (but obviously I can't work/debug :-)).
> Any hints/help/alternatives are greatly appreciated.
> Why does the debugger sense access violation while the program run standalone works fine?

Indeed. Never noticed that before.
BTW, what OS do you using ?
I see no easy solution. There's debug Makefile for MSVC 6.0, but
sources are not in MSVC compileable state. Debug version runs pretty
well in debugger on my computer. Nondebug is not, whether it's cygwin
or MSVC built.

-- 
Best regards,
 Arseny