On 19 June 2012 15:50, Sébastien Villemot <sebastien.ville...@ens.fr> wrote: > Jordi Gutiérrez Hermoso <jord...@octave.org> writes: > >> On 19 June 2012 15:31, Sébastien Villemot <sebastien.ville...@ens.fr> wrote: >>> Michael Goffioul <michael.goffi...@gmail.com> writes: >>> >>>> I have no problem using it with Java7 under windows. I would suggest >>>> to run octave in valgrind and look for suspicious messages. >>> >>> I have indeed invalid writes / unitialized values under valgrind. >> >> How about showing us where this is happening? :-) >>
>> Let's see some valgrind output... > > For example if java is compiled against GCJ 4.7: > > octave:1> pkg list > Package Name | Version | Installation directory > --------------+---------+----------------------- > java *| 1.2.8 | /usr/share/octave/packages/java-1.2.8 > octave:2> javaclasspath > Trying to create JVM > panic: Abandon -- stopping myself... > attempting to save variables to `octave-core'... > save to `octave-core' complete > Abandon > > (the message "Trying to create JVM" was added by myself in the source) > > I attach a GDB backtrace and a valgrind log. Sigh, this is from an optimised build. It's half useless. I guess I'll have to produce my own stack trace and valgrind output in a debug build. I don't see any Octave source code in the valgrind output except at a location that points to a line in a source file that doesn't seem to exist. So how urgently do we need this fix? And who's paying for it? - Jordi G. H. ------------------------------------------------------------------------------ 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
