At 05:26 PM 10/9/00 -0600, Eric Pan wrote:
>I am using NT4SP5, GNU Emacs 20.3.1, JDK1.3, and JDE 2.2.5 upgrading from
>JDE 2.1.9. I have added elib1.0 needed by 2.2.5. However, JDEBug is using
>too much system resources, so I still prefer using the oldjdb from
>the JDK. However, after I have "M-x customize-variable" on
>"jde-db-debugger" using "Other" with command "oldjdb" and "Executable". I
>got the following when I type "C-c C-v C-d"
>
>cd c:/gnu/tomcat/src/org/apache/tomcat/startup/
>oldjdb oldjdb -Dtomcat.home="C:/gnu/tomcat"
>org.apache.tomcat.startup.Tomcat
>
>Initializing oldjdb...
>oldjdb not found
>> Breakpoint set in org.apache.tomcat.startup.Tomcat.main
>> run oldjdb -Dtomcat.home="C:/gnu/tomcat"
>org.apache.tomcat.startup.Tomcat
>Could not load the oldjdb class.
>>
>
>
>Is this a bug in JDE2.2.5? Or I am misconfigured my JDE? Please help.
It is a bug and it has been fixed in the latest minor release
(JDE 2.2.5.2) available on the JDE website. However, if you want
to use oldjdb with JDK 1.3, you should select the oldjdb option
for jde-db-debugger and rename oldjdb to jdb (rename the new version
of jdb that comes with JDK 1.3 to something else). This is necessary
to ensure that the JDE can understand the oldjdb messages.
I'm sorry if this is confusing, but I haven't had time to
update the JDE to handle the case where the user has both
the new jdb and the oldjdb installed on their system and
chooses to use the oldjdb.
- Paul
