I was able to build a debug version of Tcl Blend with MSVC++ 6.0(?)
and Tcl 8.x last summer when I was tracking down some of the threading
problems with JDK1.2.  It is not that hard to build a debug version,
basically you need to build a debug version of Tcl, and then start
adding the Tcl Blend .c files to the project.  I don't have a copy
of my project file anymore, basically it was a hack.

You may find it easier to build a version of Tcl that has Tcl Blend
built in, rather than loading it at runtime.

I don't think that there is a publicaly available debug version of
jvm.dll, at least I did not find one.

I've found that Tcl Blend tends to crash when starting up at the
slightest provocation, since the designers of the JNI decided for
speed instead of safety (probably the right choice) .

Tcl Blend with JDK1.2 crashes if the path is not set up properly.
We've tried to make allowances for this, but there are too many ways
to have problems. 

I have some notes about debugging at:
http://ptolemy.eecs.berkeley.edu/~cxh/java/tclblend/troubleshooting.html
JDK1.2 has better support for debugging be setting flags when the
virtual machine is created.

I don't have access to TclPro, so I did not build the installer to
take it into account.  When I was using Installwizard, I did not
see an easy way to call tclsh80 and get back the value of the
tcl_library variable, which would make it easier to handle the various 
versions of Tcl.  I believe that the problem here is that
Installwizard is looking at the registry and it is not seeing the
TclPro keys. 

Thanks for the nit about jvm.lib vs. jvm.dll, I fixed src/pkgIndex.tcl
file.

-Christopher


--------

    I installed TclBlend1.1.1 with TclPro at work. It works fine with the
    regular protclsh and prowish shells, but I get a fatal memory reference
    error when I do a "package require java" in the debug versions of
    protclsh and prowish. This isn't surprising, since tclblend.dll is not
    linked with the MSVC debug library (msvcrtd.dll) and neither is jvm.dll.
    But is it possible to build a debug version of TclBlend? Is there even a
    debug version of jvm.dll? This issue must come up in other JNI
    programming when people want to build debug versions of their dll's, but
    I haven't seen any documentation on it.
    
    A couple of minor issues: the Windows TclBlend1.1.1 installation doesn't
    seem to recognize TclPro as a tcl installation (prompts for the location
    of the tcl installation and then gives a warning after you provide it),
    and if you don't have PATH set correctly, the warning from "package
    require java" suggests that "jvm.lib" needs to be in your PATH. Should
    be "jvm.dll".
    
    
    --
    
    Phil Chu
    [EMAIL PROTECTED]     http://www.technicat.com/
    
--------

----------------------------------------------------------------
The TclJava mailing list is sponsored by WebNet Technologies.
To subscribe:    send mail to [EMAIL PROTECTED]  
                 with the word SUBSCRIBE as the subject.
To unsubscribe:  send mail to [EMAIL PROTECTED] 
                 with the word UNSUBSCRIBE as the subject.
To send to the list, send email to '[EMAIL PROTECTED]'. 
A list archive is at: http://www.findmail.com/listsaver/tcldallas/

Reply via email to