Menu
▾
▴
#119 Debugger resumes/resets after breakpoint inactivity (1.3)
We're well aware that the interactions JVM can sometimes abort
after the machine awakes from sleep, but I just had it abort for me
while actively working with it for a long period of time. In fact, I
was in the midst of running the debugger. I was working with
DrJava continuously for the half-hour before it happened.
This may be specific to OS X; it's not clear. I don't know of any
way to reliably reproduce the problem.
-- Eric
Logged In: YES
user_id=429731
I think this may be an issue with the debugger in OS X. I
think I've seen this happen, and I know there's an issue
with breakpoints-- if you hit a breakpoint in OS X and leave
it alone for just a few minutes, it will spontaneously resume.
This is very bad, and I'm not sure if it's something in our
code or in Apple's JPDA. It should be easy to test a
different Java editor or debugger in OS X to see if it has
the same problem.
For what it's worth, I've never seen the Interactions JVM
spontaneously restart on any platform except OS X, unless
it's a laptop coming out of sleep.
Logged In: YES
user_id=429731
Bad news on this-- I tested JSwat on OS X, and it does not spontaneously resume after a breakpoint is hit, as DrJava does. Time to investigate DrJava's debugger and event handler to see if something might be setting it off inadvertently.
Oh, and I've seen the Interactions pane reset after a random resume as well, though it isn't consistent. Hopefully we can kill two birds with one stone.
Logged In: YES
user_id=429731
Updating the title of this bug. Most of the problems with
interactions resetting have been resolved, but there still
is a problem with the debugger.
We should investigate why the debugger is spontaneously
resuming when a breakpoint is hit, perhaps by creating a
more verbose mode on EventHandler to see what events are
coming in from JPDA.
Logged In: YES
user_id=429731
I just observed this behavior in JDK 1.3 on Linux- I left
the debugger at a breakpoint and it spontaneously resumed a
few minutes later. I checked on OS X, and it spontaneously
resumed in JDK 1.3.1, but not in 1.4.1. (Interestingly, it
reset the Interactions Pane on both platforms in 1.3, but on
Linux it was with a status code of 0, and on OS X it was
with a status code of 10.)
I'm going to reclassify this as a problem with JDK 1.3, not
with OS X. We'll keep the bug open, but it's not quite as
high a priority, since there's a workaround (use 1.4).
Charlie