Re: pending optiminterp-0.3.5 release

[Dmitri A. Sergatskov]

On Sun, Aug 20, 2017 at 10:51 AM, Oliver Heimlich <address@hidden> wrote:

>
> The cause of the segfault must be that something is wrong with the
> initialization of global variables. Since these seem to be defined in
> Fortran code, I can't try to inspect the code to find the cause. But
> the fact that the segfault didn't occur at your machine indicates that
> the reason is undefined order of initialization: If the initialization
> of any global variable accesses another global variable, this should
> possibly be coded differently (in C this would have to be coded with
> static variables in functions).

I can't confirm this problem on my computer.  I do not see warnings
during installation.  I can load optiminterp in Octave and run the
example_optiminterp function without errors.

I am not familiar with Fortran.  Could this be a compiler problem?  I am
testing on Debian Jessie with GCC 4.9.2.

​I do not get segfault, but running ​test_optiminterp_err resultsin:

octave:1> test_optiminterp_err
Testing 2D-optimal interpolation (analysis and error field): error: unexpected large RMS difference (analysis)
error: called from
    test_optiminterp_err at line 96 column 3
octave:1> rms
rms =  0.11872
octave:2>

 

Oliver

​Dmitri.

--

​