On Wed, Jun 20, 2012 at 08:17:58AM +0200, Sébastien Villemot wrote:
> Still I’m clueless about what’s corrupting the memory under OpenJDK
> 7. The valgrind log does not differ from the one that I obtain under
> OpenJDK 6. JWE has kindly volunteered to help, maybe there is some hope
> :)
This is probably not very helpful, but I see no problem whatsoever here
(java 1.2.8 package with the patch from Debian applied so that it finds
the libjm.so file):
=======================================================================
$ env | grep JAVA
JAVA_HOME=/usr/lib/jvm/java-7-openjdk-amd64
octave:1> javaclasspath
STATIC JAVA PATH
- empty -
DYNAMIC JAVA PATH
- empty -
octave:2> l = java_new('java.util.ArrayList'); l.add(10); l.toString()
ans = [10.0]
=======================================================================
It also doesn't crash with the io package:
=======================================================================
octave:1> pkg list
Package Name | Version | Installation directory
--------------+---------+-----------------------
io *| 1.0.18 | /home/weber/octave/io-1.0.18
java *| 1.2.8 | /home/weber/octave/java-1.2.8
=======================================================================
This is a non-optimized build of octave 3.6.2, with the latest openjdk-7
packages. Sébastien, can you try again - maybe it was just fixed in the
latest openjdk package.
Thomas
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Octave-dev mailing list
Octave-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/octave-dev
