A Java memory profiler. Check README for details. For But basically: java -Xrunjmp my.fine.java.Program. You can use GJL_DEBUG=1 <wrapper> to get the exact command line needed to launcher your program and add -Xrunjmp there. Like: betelgeuse@pena /usr/portage $ GJL_DEBUG=1 azureus using /home/betelgeuse/.azureus/gentoo.config Calling: gjl --package azureus --get-args --get-vm Using: Running: exec java -classpath .:/usr/share/bcprov/lib/bcprov.jar:/usr/share/commons-logging/lib/commons-logging.jar:/usr/share/swt-3/lib/swt.jar:/usr/share/junit/lib/junit.jar:/usr/share/sun-jaf/lib/activation.jar:/usr/share/log4j/lib/log4j.jar:/usr/share/commons-lang/lib/commons-lang.jar:/usr/share/sun-javamail/lib/mail.jar:/usr/share/azureus/lib/Azureus2.jar:/usr/share/commons-cli-1/lib/commons-cli.jar -Djava.library.path=/usr/lib -Dazureus.install.path=/home/betelgeuse/.azureus/ org.gudy.azureus2.ui.common.Main --ui=swt
Azureus seems to be bad test case as the memory profiler slows it down so that SWT can't properly communicate with X11 any more.
x86 stable
ppc stable
amd64 stable, closing