octave-maintainers
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Segfault with Java and "make check"


From: John W. Eaton
Subject: Re: Segfault with Java and "make check"
Date: Fri, 01 Feb 2013 11:11:48 -0600
User-agent: Mozilla/5.0 (X11; Linux i686; rv:10.0.11) Gecko/20121123 Icedove/10.0.11

Oops, I forgot to CC the list.

jwe


-------- Original Message --------
Subject: Re: Segfault with Java and "make check"
Date: Fri, 01 Feb 2013 11:07:12 -0600
From: John W. Eaton <address@hidden>
To: Rik <address@hidden>
CC: address@hidden

On 02/01/2013 10:40 AM, Rik wrote:

This seems like  a reasonable supposition.  The quadcc algorithm uses
adaptive rules which involve recursively subdividing the integration
region.  When the function is smooth the process doesn't go very far.
Around singularities or discontinuities the algorithm has to shrink the
integration step size to small values to ensure it maintains the overall
accuracy desired.  This would mean lots of recursion.

The JVM is not supposed to be loaded unless it is actually needed.  Is
there some test that runs prior to the one that fails that causes the
JVM to be loaded?  Can you simply skip that set of tests (delete them)
and see if that avoids the problem?  If so, then that would also be
consistent with the observation that the tests fail when running make
check (which presumably causes the JVM to be loaded) but they don't fail
when running the quadcc test by itself in a new Octave session.

jwe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]