From:	khan AT xraylith DOT wisc DOT edu (Mumit Khan)
Subject:	Re: Gnu-Win32 and Tcl/Tk
16 Dec 1996 09:00:48 -0800 :
Sender:	daemon AT cygnus DOT com
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<9612161535.AA01092.cygnus.gnu-win32@modi.xraylith.wisc.edu>
Original-To:	hamel AT republique DOT saclay DOT cea DOT fr (jl Hamel)
Original-Cc:	gnu-win32 AT cygnus DOT com
In-Reply-To:	Your message of "Mon, 16 Dec 1996 09:10:20 +0100."
	<199612160810 DOT JAA21705 AT republique DOT saclay DOT cea DOT fr>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

hamel AT republique DOT saclay DOT cea DOT fr (jl Hamel) writes:
> 
> >did you make an exe linked against the dll, or did you make a dll
> >which you then loaded with tcl/tk?
> 
> I made an exe, not a dll.
> This exe works OK (all the dll calls seems correctly understood) but
> crashes when it ends.
> 

Maybe it's crashing at the end when the interpreter is deleted and Tcl 
is in turn deleting its local storage? I believe someone else has already 
mentioned the problem with using Borland C++ DLLs with other compilers 
due to the memory allocation routines that are different. You have to use 
TCL_VOLATILE or TCL_STATIC for all objects that are passed to Tcl_* 
routines to avoid the conflict.

I'd be very interested in how you've gotten as far as you have. I know I
didn't come close to actually building the .EXE. Are you using include
files that didn't come with gnu-win32 b17? Would be great if you could
outline what you've done.

Thanks in advance,
Mumit -- khan AT xraylith DOT wisc DOT edu
http://www.xraylith.wisc.edu/~khan/
-
For help on using this list, send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -