>>>>
Hi Paul,<<<<
The time came to start Java development . I chose your tool since I like emacs.
I came across a few problems trying to make the debugger JDEbug work.
The documentation is very little so I tried to see what other people on the mailing list
have to say.
The debugger is in beta. I plan to write documentation when all features are implemented. It would be nice to have the documentation written in parallel, but I am the person doing most of the work on this project and I do not have unlimited time.
>>>>
I run JDE on Linux and the list is mainly focused on Windows.<<<<
Only becaue Windows is (still) the preponderant platform used by Java developers.
>>>>
So let's go to the point.<<<<
1) I could not start JDEbug even I looked what other people's .emacs posted yesterday.
I tracked down the problem in the *JDEbug* buffer.
java -classpath /archive/programming/JDE/jde-2.1.6beta17/java/classes:/usr/local/jdk1.2/lib/jpda.jar -Xdebug -Xnoagent -Xrunjdwp:transport=dt_socket,address=2112,server=y,suspend=n jde.debugger.Main
Exception in thread "main" java.lang.NoClassDefFoundError: jde/debugger/Main
it looks like you are setting the classpath for jdebug to <JDE-root>/java/classes which comes empty instead <JDE-root>/java/lib/jde.jar as i think it should be.
It looks like you set the jde-bug-debugger switch on. This switch is for people who are developing debugger features--not for the general user. Please turn the switch off and you will have no problems.
>>>>
2) I took jde.jar and unjar-ed it in the classes directories . This time the debugger started but not for long . The output is below.<<<<
Unnecessary.
>>>>
starting from JDE->Debug App<<<<
This command starts the debugger, sets any breakpoints you have previously specified, and issues a run command.
>>>>
*** Debugger Output for Process MenuFrame(1) ***<<<<
Launched VM Java Debug Interface (Reference Implementation) version 1.0
Java Debug Wire Protocol (Reference Implementation) version 1.0
JVM Debug Interface version 1.0
JVM version 1.2.2-RC2 (Classic VM, build 1.2.2-RC2-K, green threads, nojit)
Launching vm to run MenuFrame
Running MenuFrame.
vm started...
All threads suspended...
Application I/O closed
Input error; application I/O closed
Application I/O closed
MenuFrame process ended.
vm disconnected...
You did not set any breakpoints. Hence your app ran to completion without stopping.
>>>>
[snip]>>>>
if I start JDEbug->Processes->Launch Process does not exit but remain in a suspended state , the<<<<
You can now enter any debugger command that works in the suspended state, incluing the Continue command. It is a good idea to set a breakpoint before executing the Continue command.
>>>>
output is below<<<<
[snip]
3) What is JMaker ? I have seen some settings about it . It does not appear in my emacs frame.<<<<
JMaker is a contributed tool that creates a makefile for a package. See the Contributed Software page on the JDE website.
- Paul
