Hi Troy, Thanks for pointing out these problems. I will try to fix them ASAP.
Paul Troy Daniels writes: > Hello, > > It looks like JDEbug needs to have some methods synchronized. I tried > setting a breakpoint while the process was running, and got the following > in the Message window: > > >Setting breakpoint at line 85 in > >d:/jaguar_te1.2/KBR_ISD_VOB/Jaguar_Plan_Generator_Component/source/PhysicalNetworkBuilder/com/alphatech/kbr/jaguar/networkbuilder/SpatialSpec.java. > >Error: evaluating debugger output caused a Lisp error. > > See *messages* buffer for details. > >Error: evaluating output from the debugger caused a Lisp error. > >Debugger output: it.framework.TestSuite" "TestSuite.java" 208 "runTest") > >(list 25 "junit.framework.TestSuite" "TestSuite.java" 203 "run"). > >Lisp error: (void-variable it.framework.TestSuite) > >Breakpoint set at line 85 in class > >d:/jaguar_te1.2/KBR_ISD_VOB/Jaguar_Plan_Generator_Component/source/PhysicalNetworkBuilder/com/alphatech/kbr/jaguar/networkbuilder/SpatialSpec.java. > > It also appears that, at least with JDK 1.4.2, there is a lot of useless > traffic going from Java to emacs. My *JDEBug* buffer is full of output > that looks like > > >(jde-dbo-event-set 1 "none" > > (list "Thread" 1 "main" "runnable" "suspended by debugger" > > (list > > <stack traces of several threads> ))) > > Since jde-dbo-event-set is a no-op if the optional fourth arg is omitted, > this slows down the debugger considerably. If the java side checked for > the fourth argument, is could avoid a lot of toString calls, bandwidth to > Emacs and parsing of the string by Emacs. > > Troy > > > ---------------------------------------- > Troy Daniels > [EMAIL PROTECTED] > 781-273-3388 x218 >
