At 03:01 PM 4/25/00 -0500, you wrote:
>At 12:14 PM 4/19/00 -0400, Paul Kinnucan wrote:
>> >> >6. I get a java window when running JDEbug, and I think it's from the
>> >> >debugger, not the debuggee as it is still present after the debuggee
>> >> >terminates. Could this use javaw or, alternately, minimize the window?
>> >> >
>> >>
>> >>Set jde-run-java-vm-w to javaw. This is the default by the way. You must
>> >>have changed it when you were using NT/XEmacs.
>> >
>> >Still seeing this with jde-run-java-vm-w set to javaw. Here's my config:
>> >
>>
>>[snip]
>>
>> jde-bug-vm-executable '("java")
>> ^^^^^
>
>
>Set this to
>
> jde-bug-vm-executable '("javaw")
>
>and still get the window. Note that if I change the value of
>jde-run-java-vm to javaw, JDEbug's window doesn't appear.
>
There is no need to do this. There is something wrong with your setup.
>Was poking through the code in jde-bug.el and it finally whacked me on the
>head that there is a JDEBug -> Process -> Start Debugger option. I've
>always been starting with JDB -> Debug App. Is there a difference? In
>fiddling around for a minute, it seems that if I do JDEbug -> Process ->
>Start Debugger and then JDEBug -> Process -> Launch Process, it seems to
>run my app but breakpoints don't have any effect. Am I starting the wrong
way?
>
The JDE user's guide that comes with beta 3 discusses the various ways to
start processes in the debugger and the differences among them:
Launching a Process
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.
� JDE->Debug App This command performs the following actions:
Starts the debugger, if necessary.
Launches the application.
Sets any breakpoints you have previously specified (see Setting Breakpoints).
Runs the application.
Note With this command, the application will simply run to completion
without stopping, if you have not previously specified any valid
breakpoints for the application or none of the breakpoints exist on the
main execution path.
Issuing either of these commands cause JDEBug to split your Emacs frame
into three windows.
.[]
The top window displays a Java source buffer. The source buffer displays
either the source buffer where you launched the application or, if you used
the Debug App command, the source buffer containing the first breakpoint
hit after the application was launched.
The middle window displays the application process's local variables
buffer. The buffer displays the local variables in the stack frame of the
initial breakpoint hit when you launched the application. If your
application does not hit a breakpoint at startup, the local variables
buffer displays nothing.
The bottom window contains the debugger messages buffer for the process
that was just launched. This buffer displays messages regarding the status
of the process being debugged.
At this point, if the process was launched successfully and did not run to
completion, you can begin debugging your application.
See Also
Working with Process Buffers
Debugging Multiple Processes
- Paul
------------------------------------------------------------
TECH SUPPORT POLICY
I respond only to requests that contain a complete problem report. The
easiest way to ensure that your report is complete is to include the output
of the JDE->Help->Submit Problem Report command in your request.
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
JDE website: http://sunsite.auc.dk/jde/
JDE mailing list archive:
http://www.mail-archive.com/[email protected]/maillist.html
