Hi all,
Sebastien Vezina has worked hard at making sure that DestroyJavaVM()
releases all memory resources allocated by SableVM.
To help tracking leaked memory, he also implemented a new
--enable-memory-debugging configure option. You can find more
information about it in doc/memory-debugging.txt .
This work has been added into the trunk. So, for those working on x86
platform, you can try:
$ svn co svn://svn.sablevm.org/sablevm/trunk sablevm
$ cd sablevm
$ ./autogen.sh
$ ./configure ... # add your options, such as --enable-memory-debugging
$ make
$ su
$ make install
$ exit
$ /usr/local/bin/java-sablevm ...
For those on non-x86 platform, you should use the following branch that
tracks trunk improvements (as the trunk is currently broken on these
architectures due to the ongoing Harmony transition):
$ svn co svn://svn.sablevm.org/sablevm/branches/sablevm-lgpl
$ ...
Thank you in advance for testing this code and report back any problem.
Have fun!
Etienne
--
Etienne M. Gagnon, Ph.D.
http://www.info2.uqam.ca/~egagnon/SableVM:
http://www.sablevm.org/SableCC:
http://www.sablecc.org/ _______________________________________________
SableVM-devel mailing list
SableVM-devel@...
http://sablevm.org/lists/control/listinfo/sablevm-devel