At 06:23 PM 9/21/00 +1000, you wrote:
[snip]
>> Hi James,
>>
>> Here is the relevant section from the JDEbug User's Guide:
[snip]
>>
>> Could you please explain to me what you find puzzling or unclear about
>> this
>> explanation so that I can improve it for future releases of the JDE?
>
[snip]
>
>The explanation was quite clear.
Great!
[snip]
>> If you find this explanation clear, could you please explain exactly
>> what
>> steps you took to set breakpoints and turn the application?
>>
>
>I did use JDEbug->"Toggle Breakpoint" both before and after launching
>JDEbug. This cause the yellow/Cyan highlighting on the appropriate
>lines.
>
Excellent!
[snip]
The bug report you filed (see excerpt below) is completely normal for a
debug session in which the menu command JDE->Debug App was executed
without first setting a breakpoint. If you had set a breakpoint first, the
Debug App command would have, as I explain in the user guide, issued a set
breakpoint command to the debugger and this command would have appeared in
the transcript of the JDEbug session included in your problem report. The
fact that no such command appears means that you did not set a breakpoint
before selecting Debug App from the menu and hence the process simply ran
to completion as explained in the user's guide.
Based on the information you yourself have provided, the explanation given
in the user's guide on how to start a debug session with an initial
breakpoint is clear and the JDEbug is responding correctly to your commands.
Consequently, I do not understand your bafflement. I am baffled too.
- Paul
>========================================================================
>
>Please enter the details of your bug report here
>
>-------------------------------------------------------------------------
>
>Emacs : GNU Emacs 20.5.1 (i386-redhat-linux-gnu, X toolkit)
> of Tue Feb 22 2000 on porky.devel.redhat.com
>Package: JDE version 2.2.4.1
[snip]
>The contents of the *JDEBug* buffer were
>
>cd ~/java/ora/examples/
>java -classpath
>/home/sinnamon/emacs/site/jde-2.2.4/java/src:/home/sinnamon/emacs/site/jde-2
>.2.4/java/lib/jde.jar:/usr/local/jdk1_2_2/lib/jpda.jar jde.debugger.Main
>
>
>(jde-dbo-init-debug-session)
>
>JDE> -1 1 launch 1 -vmexec java -home /usr/local/jdk1_2_2/jre/ Sieve 2500
>
>
>(jde-dbo-message
>1 "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.2.2 (Classic VM, build Linux_JDK_1.2.2_RC4, native threads,
>nojit)")
>
>
>(jde-dbo-message 1 "initSIOConnect: starting standard I/O handshake.")
>
>
>(jde-dbo-message 1 "initSIOConnect: starting SIO connect thread.")
>
>
>(jde-dbo-message
>1 "Debugger waiting for Emacs to connect to app SIO port 2683.")
>
>
>(jde-dbo-command-result 1 2683)
>
>
>(jde-dbo-event-set
>1 "all"
>(list "Thread" 1 "main" "waiting" "suspended by debugger"
>(list)
>(list)
>nil)
>(list 'jde-dbo-vm-start-event))
>
>
>(jde-dbo-message 1 "Debugger connected to standard I/O socket.")
>
>JDE> 1 2 run
>
>
>(jde-dbo-command-result 2)
>
>
>(jde-dbo-event-set 1 "none" nil
>(list 'jde-dbo-vm-death-event))
>
>
>(jde-dbo-message 1 "Closed transport for application's standard output.")
>
>
>(jde-dbo-event-set 1 "none" nil
>(list 'jde-dbo-vm-disconnected-event))
>
>
>
>
>End Insert *JDEbug* buffer
>
>
>The contents of the CLI buffer are
>
>The largest prime less than or equal to 2500 is 2477
>
>
>
>End Insert CLI buffer
>
