EVALUATION

http://hg.openjdk.java.net/jdk7/build/hotspot/rev/cb2d0a362639
                                     

EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-gc/hotspot/rev/cb2d0a362639
                                     

EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-comp/hotspot/rev/cb2d0a362639
                                     

EVALUATION

http://hg.openjdk.java.net/jdk7/hotspot-rt/hotspot/rev/cb2d0a362639
                                     

SUGGESTED FIX

Some more description of how the launcher script on Linux and Solaris works:

If the first parameter is either "-gdb" or "-gud", HotSpot will be
launched inside gdb. "-gud" means "open an Emacs window and run gdb
inside Emacs".

Solaris: If the first parameter is "-dbx", HotSpot will be launched inside dbx.

If the first parameter is "-valgrind", HotSpot will be launched
inside Valgrind (http://valgrind.kde.org) using the Memcheck skin,
and with memory leak detection enabled.  This currently (2005jan19)
requires at least Valgrind 2.3.0.  -Xmx16m will also be passed as
the first parameter to HotSpot, since lowering HotSpot's memory
consumption makes execution inside of Valgrind *a lot* faster.
                                     

SUGGESTED FIX

Create a new launcher called fusion(.exe). On linux/solaris it will be script that sets up the environment and then launches the old gamma launcher. On windows it will be an executable.

The new launcher will be insensitive to current directory and will only need the JAVA_HOME env variable to be set up. 

On solaris/linux it will also have parameters to launch the process in a debugger.
*** (#1 of 1): [ UNSAVED ] ###@###.###
                                     

EVALUATION

Ok.