On Tue, Jun 19, 2012 at 9:50 PM, Jordi Gutiérrez Hermoso <jord...@octave.org
> wrote:
> >> 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.
> >
> > Which file?
>
> The valgrind output is pointing to __java__.cc:523, but that's a
> comment line in the Java package.
>
It's crashing at the create_jvm call, that is JNI_CreateJavaJVM. To be
honest, I don't know why it's crashing, but I'd suspect some
incompatibility with GCJ. That code has worked for years with Sun/Oracle
java.
>
> >> So how urgently do we need this fix? And who's paying for it?
> >
> > It is relatively urgent (a few weeks) if we want the java package in
> > Debian.
>
> Hm, I don't personally care too much about this package. But I suspect
> Goffioul doesn't care too much about Debian either (and I think he's
> busy right now with personal affairs).
>
It's not really that I care or not, but as long as I can't reproduce the
issue, it's hard to fix it.
Michael.
------------------------------------------------------------------------------
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
