>>>>
RE: JDE2.1.6beta8 Available<<<<
I've downloaded the b8 beta and am running on WINNTsp5, JDK 1.2.1 w/ Hotspot, Emacs 20.4.
I have some questions/bugs:
1) Perhaps I misunderstood your instructions, but I cannot set a breakpoint and then start the debugger. I have to start the debugger, launch the process, and then set the breakpoint. While this seems logical, the instructions say that the breakpoint can be set first.
You could to this in previous releases, but not in the current release because of a
regression bug. The next release will fix this.
>>>>
2) When I use set breakpoint, it get the line number one less than it should. If I put the cursor at the beginning of line 248 and select the menu item set breakpoint, the message reports the breakpoint at 247. Obviously the workaround is to set the breakpoint at the next line.<<<<
There must be a bug in my line determination algorithm, although it works fine with my
source. Do you have any extra line feeds at the beginning or end of your files?
>>>>
3) After I hit the breakpoint at line 248 and the '=>' appears at the correct line., I selected "step over" and the '=>' doesn't advance and I get the following message: "Breakpoint hit at line 248 in com.luna.server.Server (Server.java) on thread main. All threads suspended." I do this again and again the arrow doesn't move and I get the same message, but its obvious from the process output that the program has continued. Doing step over again gives the following:<<<<
Error: evaluating debugger output caused a Lisp error.
See *messages* buffer for details.
Error: unable to step into... .
Reason: The specified thread is not suspended
Is stepping working yet? The messages file yields:
It works on my one test program. I'm sure there are plenty of bugs to be worked out. That's
why this is a beta release, actually more like a very early alpha.
>>>>
<<<<
It's impossible to tell what's going on without seeing your .emacs (and prj.el file, if you
use one) as well as the contents of the *JDEbug* buffer. The arrow cursor not moving could be because you did not specify your source paths in jde-db-source-directories, though you should
have gotten a prompt if the JDE could not find the source file. The exception could have occurred because you stepped into a different thread and the JDE did not recognize this fact, which would be a bug. But this is all idle speculation in the absence of more information.
>>>>
Error: evaluating output from the debugger caused a Lisp error.<<<<
Debugger output:
(jde-dbo-debug "
jde.debugger.JDEException: The specified thread is not suspended
at jde.debugger.SpecCommands.doStep(SpecCommands.java:410)
at jde.debugger.Application.handleCommand(Application.java:772)
at jde.debugger.Jdebug.handleAppCommand(Jdebug.java:357)
at jde.debugger.Jdebug.access$1(Jdebug.java:337)
at jde.debugger.Jdebug$1.run(Jdebug.java:215)
").
Lisp error: (wrong-number-of-arguments (lambda (proc-id debug-info) (jde-dbs-display-debug-message proc-id debug-info))
4) Anyway to suspend the running threads? In general is there a way to interact directly with
Not yet but soon there will be.
>>>>
the debugger (oh no, not a command line, ahh) so that I can work around bugs or unimplemented features in JDEbug?<<<<
Yes, you can enter commands directly in *JDEBug*. But be prepared to parse Lisp because that's what the debugger outputs.
>>>>
Thanks
� __o�� Brian G. Anderson
�_'\<,� Luna Information Systems
(:)/(:)� (510)285-0304
