At 10:58 AM 3/7/00 +0100, Harald Maier SIG wrote:
>
>Paul Kinnucan <[EMAIL PROTECTED]> writes:
>
>> At 01:52 AM 2/21/00 -0800, you wrote:
>> >Hi Paul,
>> >
>> >Sorry to have to trouble you, but I've been unable to resolve this
>> >problem after several hours of failed attempts to do so.
>> >
>> >I've tried JDE 2.1.6beta20 on several different "platforms", namely,
>> >
>> >Redhat Linux 6.1 XEmacs 20.4
>> >Redhat Linux 6.1 Emacs 20.4.1
>> >Windows NT Server 4.0 OptionPack 6 NTEmacs 20.5.1
>> >
>> >Of the three, only with the latter have I successfully been able to
>> >debug an application.
>> >
>> >
>>
>> You are probably using JDK 1.2.2 on Linux. I believe, from hearsay (I do
>> not have access to Linux), that this port, unlike the Windows port,
>> provides the new JDPA-based version of jdb whose output differs just enough
>> from the old version to completely confuse the JDE. If this is the case,
>> your options are to set jde-db-debugger to oldjdb, if this is included in
>> your JDK distribution (as it is with JDK 1.3 on other platforms), or to use
>> the JDE's new JDEbug debugger.
>>
>
>Personally, I have installed the latest JDK 1.2.2 from (I believe Jan,
>20) on a Suse 6.1 system with JDE 2.1.6beta20 and emacs 20.5. That
>linux system needs upgrading to the glibc 2.1. After that work it
>seems that the linux version is similar to the WindowsNT version
>except that the windows version of the JDK gives more hints (with
>message boxes) about the environment.
>
Does the JDK bin directory contain an executable named oldjdb?
- Paul
