==> At 03:49 PM 9/20/99 -0500, you wrote:
==> >Paul,
==> >
==> >Thanks for the info on turning this option off. I turned it off only to
==> >find a bug in the JPDA/HOTSPOT combo that causes the VM to die randomly.
==> >What I would like to do is have the -classic flag set. My error results
==> >from the -classic arg not being the first argument to the VM. If I run
==> the >same command as JDEbug tries, it fails stating that the -classic is an
==> >invalid argument. If I move the -classic argument to the front of the
==> >command-line, it works as expected. Are you able to run with the -classic
==> >arg in an arbitrary possition ? I was under the impression that it had to
==> >be first. Here is my JDEbug beffer again. also attached my .emacs & a
==> >common lisp file. >
==>
==> Okay, I guess I'm confused. The reason I included the "classic-mode"
==> variable was to insures that the -classic switch is always first on the
==> command-line because I had heard that that was required. By "first" I
==> thougth this was meant
==>
==> java -classic other-args
==>
==> rather than this
==>
==> java some-args -classic some-other-args
==>
==> This is what the -classic mode switch now does.
==>
==> In the case of JDEBug, there is no way of guaranteeing that the -classic
==> switch is first on the command line. This is because JPDA constructs the
==> java command line by combining the args it needs with whatever args you
==> specify. The args that JPDA requires always go first on the command line
==> followed by the user's args. AFAIK there is no way for JDEBug to manipulate
==> this order to ensure that -classic goes before all other arguments.
Paul,
Both from my reading of the code and my tests, the user supplied
options go first, for example:
/export/1.3/build/solaris/bin/../bin/sparc/green_threads/java -classic -Xdebug
-Xnoagent -Djava.compiler=NONE
-Xrunjdwp:transport=dt_socket,address=palau:55272,suspend=y A
Can you send the generated command line.
==> Why do you have to have the -classic option anyway?
If HotSpot is loaded then HotSpot is the default, the HotSpot implementation
of JVMDI in 1.0 is only beta quality and has some serious bugs. To get
around this you need the -classic option.
-Robert
==> - Paul
