Hi all,
Are there any problems running JDebug with jdk1.3 and solaris8(Intel)
(using jde-2.2.1 and GNU Emacs-20.7).
I followed the instructions in the docs and can single step
in the debugger for a while, but eventually get timeout errors
(the application also runs quite slowly in the debugger).
The error message is:
"No response to command 15. (process 1; timeout 10 sec.)"
and the JDebug process window contains:
-------------
*** Debugger Output for Process jsky.app.ot.OT(1) ***
Launch command line:
java -classpath
/export/home/abrighto/work/ot/classes:/export/home/abrighto/work/jsky/classes:/export/home/abrighto/work/ot/lib/junit.jar:/export/home/abrighto/work/ot/lib/jdom-b4.jar:/export/home/abrighto/work/jsky/lib/graph.jar:/export/home/abrighto/work/jsky/lib/xerces.jar:/export/home/abrighto/work/jsky/lib/diva.jar:/export/home/abrighto/work/jsky/lib/jacl.jar:/export/home/abrighto/work/jsky/lib/tcljava.jar:/export/home/abrighto/work/jsky/lib/fits.jar:/export/home/abrighto/work/jsky/lib/image.jar:/export/home/abrighto/work/jsky/lib/util.jar
-Xmx128m jsky.app.ot.OT
Emacs connected to standard IO port 32883 for process jsky.app.ot.OT.
Launched VM Java Debug Interface (Reference Implementation) version 1.3
Java Debug Wire Protocol (Reference Implementation) version 1.0
JVM Debug Interface version 1.0
JVM version 1.3.0 (Java HotSpot(TM) Client VM, interpreted mode)
vm started...
All threads suspended...
Debugger waiting for Emacs to connect to app SIO port 32883.
Debugger connected to standard I/O socket.
Setting breakpoint at line 476 in OtTreeWidget.java.
Running jsky.app.ot.OT.
Resolved breakpoint set in OtTreeWidget.java at line 476.
Breakpoint hit at line 476 in jsky.app.ot.OtTreeWidget (OtTreeWidget.java) on thread
AWT-EventQueue-0. All threads suspended.
Stepped to line 475 in jsky.app.ot.nsp.SpItem (SpItem.java) on thread
AWT-EventQueue-0. All threads suspended.
Stepped to line 438 in jsky.app.ot.nsp.SpItem (SpItem.java) on thread
AWT-EventQueue-0. All threads suspended.
-------------
The docs say to specify classic mode, but that is not available
under jdk1.3 solaris or linux versions (there is no -classic option).
Thanks,
--
Allan Brighton
