[Pkg-octave-devel] octave-odepkg problems

Rafael Laboissiere rafael at laboissiere.net
Tue Mar 20 19:40:26 UTC 2012


* Sébastien Villemot <sebastien.villemot at ens.fr> [2012-03-20 13:30]:

> Thomas Weber <tweber at debian.org> writes:
> 
> > short list:
> >  - extremely verbose output from Fortran code during build
> >  - some more Fortran snippets during the test suite
> >  - segfault in odepkg_octsolver_mebdfdae
> >
> > Can somebody please build the package to verify the segfault?
> 
> On my amd64 machine, I can replicate the segfault in the test for
> odepkg_octsolver_mebdfdae.

I isolated the problem, which seems to occur only when the 'OutputFcn'
option is used, and posted it in octave-dev:

http://permalink.gmane.org/gmane.comp.gnu.octave.devel/6916

There is no followup yet.

My take on this is similar to my take on the problems with octave-signal:

  - The compilation of the Fortran files issue just four warnings, not so
    "extremely verbose".
  - The Fortran snipets are associated with the failure of some test
    in odepkg_octsolver_mebdfi.cc.  This is a real problem, but odebdi
    is just one of the several solvers available in odepkg.
  - The segfault in odepkg_octsolver_mebdfdae (actually in function
    odebda) seems to be a corner case.  The other tests in that
    file pass.
  - Otherwise, the huge majority of tests in the whole package pass.
    
So, I would upload odepkg anyway.
 
Rafael



More information about the Pkg-octave-devel mailing list