[Cc to mailing list.]
On Tue, 26 Sep 2006 16:46:36 +0200, "Goffioul Michael" goffioul@imec.be wrote:
I just tried with VS 2003. I started LispWorks 5.0, then attached the VS debugger to LW, then loaded RDNZL, then loaded and ran the apropos example. Finally, I quit LispWorks. I didn't get any messages, though. Maybe this only happens with .NET 2.0? Or is it specific to ECL? Or do I have to do something else? I'm not familiar with the VS debugger.
Nevertheless, it's pretty disturbing that DelegateAdapter objects are /never/ released... :(
Maybe you can try to latest binary package for the LISP shell I provided at http://sourceforge.net/projects/ecls . For me, it crashes at exit when I start the shell and open an existing LISP file in the editor.
I can't reproduce that. I tried with VS 2003 as well as with VS 2005. In both cases I started VS, then the Lisp shell, then I attached to the Lisp shell from VS. Then I opened an existing Lisp source file from the Lisp shell and afterwards quit the application.
In the case of VS 2005 the debugger window said:
The program '[3120] lispshell.exe: Managed' has exited with code 0 (0x0).
Hmmm...