Sorry, it was unintentional. This was my transmission:
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
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:
...
/
Sigh. I can do that for my testing, certainly. But you may recall that my constraint
in production is
that I am not the one that is invoking Tcl--Vignette's StoryServer product is invoking
Tcl. And they are
using Tcl 8.2.0. Not even 8.2.3. (At least that's what [info patchlevel] says.)
Mo DeJon
> When I started this project back in March, I could not get anything to work with JDK
>1.1.8, Tcl
> 8.3, and TclBlend 1.2.5, so I used Tcl 8.2.3. I do not remember now what the symptom
>was, just
> that it didn't work. (I am using JDK 1.1.8 because of warnings about JDK 1.2 at
> http://dev.scri
I repeated the test of the patch, with JDK 1.2 on Solaris. Same result...
hanging in AutomaticSignature.test.
Jiang Wu wrote:
> I am not sure about how well JDK 1.1.8 work with TclBlend. I have not
> tested TclBlend with JDK 1.1.8. Are you unable to upgrade to JDK 1.2?
>
> -- Jiang Wu
>[EM
Mo DeJong wrote:
> On Tue, 13 Jun 2000, Dr Wes Munsil wrote:
>
> > Thank you for your response. I am running "make test". (I don't know who loads
>whom, but I
> > infer from your comments that that means I am loading a JVM into Tcl.) I had
>removed the
> > MonitorEnter calls from JAVA_LOCK and
I originally chose JDK 1.1.8 because of this statement at
http://dev.scriptics.com/faq/java.html#Q2: "When Tcl Blend is compiled
with JDK1.2, it fails a few of the tests, see the known_issues.txt file in
the distributions of Tcl Blend for more details."
Jiang Wu wrote:
> I am not sure about how
I am not sure about how well JDK 1.1.8 work with TclBlend. I have not
tested TclBlend with JDK 1.1.8. Are you unable to upgrade to JDK 1.2?
-- Jiang Wu
[EMAIL PROTECTED]
-Original Message-
From: Dr Wes Munsil [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, June 13, 2000 11:31 AM
To: Jian
On Tue, 13 Jun 2000, Dr Wes Munsil wrote:
> Thank you for your response. I am running "make test". (I don't know who loads whom,
>but I
> infer from your comments that that means I am loading a JVM into Tcl.) I had removed
>the
> MonitorEnter calls from JAVA_LOCK and JAVA_UNLOCK in response to
Thank you for your response. I am running "make test". (I don't know who loads whom,
but I
infer from your comments that that means I am loading a JVM into Tcl.) I had removed
the
MonitorEnter calls from JAVA_LOCK and JAVA_UNLOCK in response to an earlier suggestion
from
Jiang Wu.
The history
On Tue, 13 Jun 2000, Dr Wes Munsil wrote:
> I would love to give the answers to your good questions off the top of my head, but I
> don't know what "make test" does and I don't know what AutomaticSignature.test does.
>I
> am just following the installation and test instructions that came with th
I would love to give the answers to your good questions off the top of my head, but I
don't know what "make test" does and I don't know what AutomaticSignature.test does. I
am just following the installation and test instructions that came with the download.
I can look into the makefile and the re
On Tue, 13 Jun 2000, Dr Wes Munsil wrote:
> I applied this patch and your other suggestion, and rebuilt, and now I cannot
> make it through the regression tests. tcljava/AutomaticSignature.test appears to
> deadlock. Can anyone help? My deadline is near, and I am close to having to
> abandon TclB
I applied this patch and your other suggestion, and rebuilt, and now I cannot
make it through the regression tests. tcljava/AutomaticSignature.test appears to
deadlock. Can anyone help? My deadline is near, and I am close to having to
abandon TclBlend as a solution, which I really do not want to h
Yes. You can download the patch from:
http://www-cs-students.stanford.edu/~jwu/tclblend.patch
Note that the patch does NOT remove the JAVA_LOCK code in TclBlend. It is
still possible to deadlock after applying the patch due to JAVA_LOCK. Your
stack trace looks JAVA_LOCK is causing the
15 matches
Mail list logo
