Adam Ambrose wrote:
> There are actually at least several of us who have successfully used
> JDEbug under Linux. What are the exact errors you are getting?
>
Thanks Adam for replying,
I woulsd like to know what are you using and what are your settings.
I can launch the debugger but it exists . Yu can look at the errors below.
Do you have by any chance the steps for success ? :- )
Thanks again,
Bogdan
I past below a message I posted about 2 weeks ago :
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.
I run JDE on Linux and the list is mainly focused on Windows.
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.
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.
starting from JDE->Debug App
*** 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...
the *JDEbug buffer shows
JDE> -1 8 launch 4 -vmexec java -home /usr/local/jdk1.2/jre -classpath
/archive/programming/jde-latest/java/lib/jde.jar MenuFrame
(jde-dbo-message
4 "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)")
(jde-dbo-command-result 8 1589)
JDE> 4 9 break absolute MenuFrame.java 41
(jde-dbo-event-set
4 "all"
(list "Thread" 1 "main" "waiting on monitor" "suspended by debugger")
(list 'jde-dbo-vm-start-event))
(jde-dbo-command-result 9 0)
JDE> 4 10 run
(jde-dbo-command-result 10)
(jde-dbo-message 4 "Application I/O closed")
(jde-dbo-error 4 "Input error; application I/O closed")
(jde-dbo-message 4 "Application I/O closed")
(jde-dbo-event-set 4 "none" nil
(list 'jde-dbo-vm-death-event))
(jde-dbo-event-set 4 "none" nil
(list 'jde-dbo-vm-disconnected-event))
JDE> -1 11 launch 5 -vmexec java -home /usr/local/jdk1.2/jre -classpath
/archive/programming/jde-latest/java/lib/jde.jar MenuFrame
if I start JDEbug->Processes->Launch Process does not exit but remain in a
suspended state , the output is below
(jde-dbo-message
5 "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)")
(jde-dbo-command-result 11 1593)
(jde-dbo-event-set
5 "all"
(list "Thread" 1 "main" "waiting on monitor" "suspended by debugger")
(list 'jde-dbo-vm-start-event))
Any help in debugging this will be greatly appreciated.
I will provide any info you think that you need. I attached the .emacs file to
the message.
