At 11:05 AM 7/5/00 -0700, you wrote:
>To: [EMAIL PROTECTED]
>Subject:
>--text follows this line--
>
>Please enter the details of your bug report here
>
>
>---------------------------------------------------------------------------
---
>
>Hi Paul,
>
>Responding to your suggestion I included the problem report.
>Again, Thanks for your help.
>
>I'm trying hard to get JDEbug to run with jde-2.1.7 and jdk1.2.2 using
>XEmacs 21.1 on Linux RedHat 6.2
>
>I have searched around for info on this problem and found an allusion
>to incompatibilities between the JRE VM and JPDA but I dont understand
>the
>issue because jdk1.2.2 has a jpda.jar
>
>Can you tell me if jde-2.1.7 and jdk1.2.2 can work together for JDEbug?
>Do I need to download jdk1.3 and set jde-bug-jpda-directory to jdk1.3
>instead?
>

Hi George,

I have personally verified that the JDE 2.1.7 version of JDEbug and JDK
1.2.2 work on Solaris and all Windows platforms. I have many reports of
users who have gotten this combo to work on Linux as well, although I have
not been able to verify this personally as I do not have access to Linux.
So whatever your problem is, I believe it is a setup problem.

 
>Here's what happens:
>I can compile and run a "test.java" OK, but after I set a breakpoint and
>
>run the debugger (JDE->Debug App) I get this message on the process
>window:
>
>*** Debugger Output for Process test(1) ***
>
>Error: debugger unable to launch test.
>  Reason: VM initialization failed for:
>/usr/local/java/jdk1.2.2/bin/java -Xdebug -Xnoagent -Djava.compiler=NONE
>
>-Xrunjdwp:transport=dt_socket,address=mars:1773,suspend=y -classpath
>/home/soler/server/projects/classes:/usr/local/java/Progress_SonicMQ/lib/cl
ient.jar:/usr/local/java/ibusjms_3_0_1/lib/iBusJMS.jar:/usr/local/java/ibusj
ms_3_0_1/lib/jndi.jar
>
>-v -verbosejni -Xmx32m -Xss1m -Xoss16m test

When ever you get a VM initialization error, you should always try to run
the command line specified in the error message (see above) in a shell.
This will tell you why the vm is unable to start. Remember run the command
line EXACTLY as it is given in the error message, i.e.,

/usr/local/java/jdk1.2.2/bin/java -Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=mars:1773,suspend=y -classpath
/home/soler/server/projects/classes:/usr/local/java/Progress_SonicMQ/lib/cli
ent.jar:/usr/local/java/ibusjms_3_0_1/lib/iBusJMS.jar:/usr/local/java/ibusjm
s_3_0_1/lib/jndi.jar -v -verbosejni -Xmx32m -Xss1m -Xoss16m test

Next I notice that your LD_LIBRARY_PATH is pointing to the library in the
Java Runtime Environment (jre), i.e.,

LD_LIBRARY_PATH=/usr/local/java/jdk1.2.2/jre/lib/i386

The JRE is intended for end users and hence its library does not include
the JDPA library, i.e., libjdwp.so. This library should be in
jdk1.1.2/lib/i386 and you should therefore include this directory in your
load path.

Finally, a user who has gotten JDEbug to work with JDK 1.2.2 on Linux has
reported that you should ensure that the following symbolic links exist on
your system:

jdk1.2.2/lib/libjdwp.so -> jdk1.2.2/lib/i386/libjdwp.so
jdk1.2.2/lib/libdt_socket.so -> jdk1.2.2/lib/i386/libdt_socket.so 

I would think this is necessary only if you set your LD_LIBRARY_Path to
jdk1.2.2/lib. However, if these links do not exist, try creating them and
see if it makes a difference.

- Paul

Reply via email to