Michael Goffioul writes:
> On Tue, Jun 19, 2012 at 11:45 PM, Sébastien Villemot
> wrote:
>
> Michael Goffioul writes:
>
> > GCJ is crashing at JVM initialization. At that point, no octave_java
> > object has been allocated yet.
>
> My understanding is that during JVM in
On Tue, Jun 19, 2012 at 11:45 PM, Sébastien Villemot <
sebastien.ville...@ens.fr> wrote:
> Michael Goffioul writes:
>
> > GCJ is crashing at JVM initialization. At that point, no octave_java
> > object has been allocated yet.
>
> My understanding is that during JVM initialization, octave_java obj
Michael Goffioul writes:
> GCJ is crashing at JVM initialization. At that point, no octave_java
> object has been allocated yet.
My understanding is that during JVM initialization, octave_java objects
*are* allocated through static java variables initalizations. Indeed, if
I comment out this lin
On Tue, Jun 19, 2012 at 11:03 PM, Sébastien Villemot <
sebastien.ville...@ens.fr> wrote:
> Michael Goffioul writes:
>
> > 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
>
Michael Goffioul writes:
> On Tue, Jun 19, 2012 at 9:50 PM, Jordi Gutiérrez Hermoso
> 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 a
On Tue, Jun 19, 2012 at 9:50 PM, Jordi Gutiérrez Hermoso 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
Jordi Gutiérrez Hermoso writes:
>> Which file?
>
> The valgrind output is pointing to __java__.cc:523, but that's a
> comment line in the Java package.
This is because I have slightly altered the original source (as
indicated in my previous email). I should have fixed that before.
>>> So how ur
On 19 June 2012 16:20, Sébastien Villemot wrote:
> Jordi Gutiérrez Hermoso writes:
>
>> On 19 June 2012 15:50, Sébastien Villemot wrote:
>>> Jordi Gutiérrez Hermoso writes:
>>>
On 19 June 2012 15:31, Sébastien Villemot
wrote:
> Michael Goffioul writes:
>
>> I have no pr
Jordi Gutiérrez Hermoso writes:
> On 19 June 2012 15:50, Sébastien Villemot wrote:
>> Jordi Gutiérrez Hermoso writes:
>>
>>> On 19 June 2012 15:31, Sébastien Villemot wrote:
Michael Goffioul writes:
> I have no problem using it with Java7 under windows. I would suggest
> to
On 19 June 2012 15:50, Sébastien Villemot wrote:
> Jordi Gutiérrez Hermoso writes:
>
>> On 19 June 2012 15:31, Sébastien Villemot wrote:
>>> Michael Goffioul writes:
>>>
I have no problem using it with Java7 under windows. I would suggest
to run octave in valgrind and look for suspici
Jordi Gutiérrez Hermoso writes:
> On 19 June 2012 15:31, Sébastien Villemot wrote:
>> Michael Goffioul 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 / unitial
Hi Sébastien
Sébastien Villemot wrote:
> Hi,
>
> I am trying to make the java package in Debian work with OpenJDK 7.
>
> This is becomig necessary because the security support of OpenJDK 6 is
> about to expire, and that version will therefore soon be removed from
> Debian (see [1]).
>
> However, t
On 19 June 2012 15:31, Sébastien Villemot wrote:
> Michael Goffioul 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 sho
Michael Goffioul 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.
These appear with several JVMs: OpenJDK 6, 7, and GCJ.
GCJ gives more
On Mon, Jun 18, 2012 at 10:26 PM, Rafael Laboissiere wrote:
> * Carnė Draug [2012-06-18 16:24]:
>
> > the new version of the vrml package is now up and should be available
> > for download (SF had some problems during the weekend but seems to have
> > been fixed now).
>
> Thanks. I prepared a D
On Tue, Jun 19, 2012 at 11:21 AM, Sébastien Villemot <
sebastien.ville...@ens.fr> wrote:
> Hi,
>
> I am trying to make the java package in Debian work with OpenJDK 7.
>
> This is becomig necessary because the security support of OpenJDK 6 is
> about to expire, and that version will therefore soon
Hi,
I am trying to make the java package in Debian work with OpenJDK 7.
This is becomig necessary because the security support of OpenJDK 6 is
about to expire, and that version will therefore soon be removed from
Debian (see [1]).
However, the java package built against OpenJDK 7 makes Octave cr
17 matches
Mail list logo
