At 11:30 AM 12/2/99 -0500, [EMAIL PROTECTED] wrote:
>
>
>> > The messages buffer shows:
>> >
>> > Error: debugger didn't respond to command:
>> > -1 1 launch 1 -use_executable c:/jdk1.2.2/bin/java -classpath
c:/usr/rankin
>> > trash
>> > [2 times]
>> > No method definition: jde-dbs-proc-display-debug-message,
>> > "#<jde-dbs-launch-process Launch trash>"
>> >
>> > ...
>>
>> For some reason JPDA does not accept an executable specified as a path. I am
>> investigating. Meanwhile, try setting jde-run-java-vm-w to javaw and, if
>> necessary, updating your system command path to include c:/jdk1.2.2/bin.
>>
>> Note: you should ALWAYS use javaw to run apps on NT under the JDE.
>
>I am seeing the same results as Rankin, even after setting
jde-run-java-vm-w to
>"javaw" and adding c:/jpda1.0/bin and c:/jdk1.2.2/bin to the system path.
I am
>running NT 4.0 and Emacs 20.4.1. I have attached (hopefully) all the relevant
>files. Any suggestions would be much appreciated.
>
Hi Michael,
You may be seeing the same result (i.e., the launch apparently failing) but
not for the same reason as Rankin. The JDE is not getting a response from
the debugger after commanding it to launch your test app. I see nothing
obviously wrong with your setup. One possibility is that javaw takes a long
time to start on your system. If the debugger does not respond to a command
within ten seconds, the JDE assumes something is wrong and gives up. If in
fact the problem is slow startup, you can fix it be customizing
jde-bug-debugger-command-timeout. Try setting the timeout factor to a large
value, say 20 seconds.
- Paul
