Mo DeJong wrote:
I suggest that you compile Tcl with debug symbol and
then attach with gdb (or try the "make gdb" rule)
to find out what JavaCmdProc() is doing to enter
a monitor. That is what is locking up
your threads.
Well, JavaCmdProc() is just calling EnterMonitor. Here's the code:
...
    /*
     * Invoke the command by calling Interp.callCommand().  Be sure to
     * leave the monitor since we are assuming nothing about the state
     * of the world after this call.
     */

    (*env)->MonitorExit(env, java.NativeLock);
    result = (*env)->CallIntMethod(env, interpObj,
            java.callCommand, cmd, args);
    exception = (*env)->ExceptionOccurred(env);
    (*env)->MonitorEnter(env, java.NativeLock);   <<<---
    if (exception) {
        (*env)->ExceptionClear(env);
    }
... ---------------------------------------------------------------- The TclJava mailing list is sponsored by Scriptics Corporation. 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]'. An archive is available at http://www.mail-archive.com/tcljava@scriptics.com

Reply via email to