>> >2. JDEbug --> Start Debugger --> Launch Process -->Set Breakpoint -->
>> > Continue is fine, but
>> >
>> > JDE --> Debug App starts the JDEbug debugger, launches a process, sets
>> > a breakpoint at the top of the program and and starts executing.
>> > There seems to be a problem clearing breakpoints that have been
>> > set in previous Launch Processes while in this mode.
>> >
>>
>> This is not exactly what happens. There is a description of what Debug App
>> does in the user's guide. Please read that and if it is not clear to you,
>> let me know so that I can improve the description.
>>
><<<<<< *********************************
>I misphrased my question here is the confusion:
>
>
> ../jde-2.1.6beta23/doc/jdebug/ug/jdebug-ug-content.html
>
>In this guide, a process refers to a running instance of an application.
>JDEBug provides two commands for launching processes.
>
>JDEbug->Processes->Launch Process
>
>This command launches an instance of the application whose main class is
>specified by the variable jde-run-application-class, or, if this variable
>is nil, the application in the current Java source buffer. The application
>stops at the first line of the application's main method, allowing you to
>set breakpoints or begin stepping through the application.
> ====
>
>The confusion is in the last line with the word `or'. It reads as if
>you could start stepping through without setting a breakpoint. This is no
>longer significant in beta23 since the step commands are now invisible but
>it may be worth clarifying.
>>>>>>>>>>>>>>>>> **********************************
>
Hi Steve,
You are absolute right. I must have been on drugs when I wrote that.
(Actually it was written in haste in a groggy state late at night.) I have
rewritten it for beta24 to make it clear what actually happens, which is
this: the debugger launches the vm that runs the application and loads the
app's main class and then suspends the vm. At this point, your options are
to set breakpoints and/or issue a Run command. Issuing the run command
causes the vm to invoke the main method of the app's main class.
Sorry for the confusion.
- Paul
