I'm running the curent stable release
(drjava-stable-20020814.jar), on Redhat Linux 7.3. I'm
using Java 1.4 SDK (java version "1.4.0_01", Java(TM) 2
Runtime Environment, Standard Edition (build
1.4.0_01-b03), Java HotSpot(TM) Client VM (build
1.4.0_01-b03, mixed mode)). I could not get the
properties info out of the About panel, as it's now a
table, and X doesn't want to grab the contents into its
buffer--tips for this?
In any case, my problem was that when I started the
debugger (click Debug-Mode in the debugging panel), I
would get an exception:
Could not start the debugger.
edu.rice.cs.drjava.model.debug.DebugException: Could
not connect to VM: java.net.ConnectException:
Connection refused.
However, this seems to have magically fixed itself
while I've been typing up this report! That is, in
trying to do this repeatedly, it has started working,
and I haven't been able to recreate the original
failure. Therefore, this report can serve to be just
informational until it happens again, and I can report
more information.
Logged In: YES
user_id=429731
Heh-- bugs always have a tendency of hiding when you try to
reproduce them, don't they? :)
Anyway, if you notice it again, try the drjava-20020906-2148
release, which includes fixes for some RMI bugs in the
stable version. Specifically, if some other process is
using either the default RMI port, there used to be problems
with the Interactions pane-- now DrJava looks for a unique,
safe port to use.
I'll set this as low priority for now, but if you notice it
again in the newer release, post an update and I'll look
into it.
Logged In: YES
user_id=429731
Have you seen this happen any more? I haven't been able to
reproduce it on any platform that I've worked on, so I'll
assume that it was resolved with the RMI fixes in that Sept.
6th release. If it occurs again, feel free to re-open this bug
report.