Hi,

I'm running solaris with jdk1.2.2 installed.

It seems that invoking the debugger on solaris works slightly different.
JDE starts the debugger with the following result :
*** Debugger Output for Process
com.acriter.flower.sample.TestApplicationController(5) ***

Error: debugger unable to launch
com.acriter.flower.sample.TestApplicationController.
  Reason: VM initialization failed for: /opt/java/jdk1.2.2/jre/bin/java
-Xdebug -Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=gravity:39629,suspend=y -xms40m
-Xmx80m com.acriter.flower.sample.TestApplicationController

I've tried the command in a shell and got this result:
/opt/java/jdk1.2.2/jre/bin/java -classic -Xdebug -Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server="y",address=gravity:38439,suspend=y
-Xms40m -Xmx80m com.acriter.flower.sample.ApplicationController
Invalid listen port number: gravity:38439
Transport dt_socket failed to initialize, rc = -1.
FATAL ERROR in native method: No transports initialized
SIGABRT   6*   abort (generated by abort(3) routine)


This command doesn't result in any errors:
/opt/java/jdk1.2.2/jre/bin/java -classic -Xdebug -Xnoagent
-Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,server="y",address=38439,suspend=y -Xms40m
-Xmx80m com.acriter.flower.sample.ApplicationController

I don't know if anyone has a small idea how to tell JDE to use the latest
command. I did some research without any success, I cannot find either
the exact statement or customization var's to controll this behaviour.

any help appreciated.

regards,

Richard

Reply via email to