At 01:36 PM 3/7/00 +0100, Harald Maier SIG wrote:
>
>Paul Kinnucan <[EMAIL PROTECTED]> writes:
[snip]
>> >>
>> >> 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?
>>
>
>Yes.
>
Then, the Linux JDK 1.2.2 is not the same as the Windows JDK 1.2.2. The
Windows JDK 1.2.2 uses the old debug architecture. That is why you have to
download the JDPA package to use JDEbug on Windows. It appears that the
Linux version has JPDA built into it. This has two consequences. You don't
have to install JPDA to use JDEbug and you cannot use (new)jdb with JDE.
You have to use oldjdb.
- Paul
