I've been using jdb (through JDE) on the Blackdown 1.2 JDK since it's been
released, and I've only gotten the problem you described when I try to run
java/jdb with native threads. When I run it with green threads and no JIT, it
works perfectly for me, if slowly.
If you haven't already, try setti
>
> > Ever try System.out.print() or the "Ctrl-\" thing?
>
>
> What is the "Ctrl-\" thing?
Ctrl-\ or SIGQUIT will give you a "thread-dump" of the jvm. Consider it
like a combination of "info threads" and "bt" in gdb rolled into one.
Plus, you can call it anytime at will. It also prints out al
Thus spake Weiqi Gao on Tue, 12 Oct 1999:
> You mean, you didn't get the
> [Internal debugger error: unexpected eof]
> Exception in thread "main" java.lang.InternalError
> at sun.tools.debug.RemoteAgent.error(Compiled Code)
> at sun.tools.debug.RemoteAgent.getReply(Compiled Code)
>
"Daniel P. Zepeda" wrote:
>
> I've been trying to use JDK 1.2prev2's jdb with no success. When I
> set a breakpoint, jdb happily continues on past the breakpoint without
> stopping.
You mean, you didn't get the
[Internal debugger error: unexpected eof]
Exception in thread "main" java.lan
