Several crash cases for build with recent sources

[Alexander Mamonov]

Hello,

I tried your patches, doing "clear all" after "backend('fltk')" no
longer crashes Octave.

My version of ARPACK is from
http://www.caam.rice.edu/software/ARPACK/SRC/arpack96.tar.gz
with this patch
http://www.caam.rice.edu/software/ARPACK/SRC/patch.tar.gz

I will try to debug the crashes of ARPACK functions (have to figure
out how gdb works, I'm a Visual Studio person, shame on me :) So far
it seems that the issue might be related to how the exceptions are
passed from the dynamically linked modules. I don't think there is any
problem with ARPACK itself.

Regards,
Alex

On Tue, May 19, 2009 at 12:57 PM, John W. Eaton <jwe at octave.org> wrote:
> On 11-May-2009, Alexander Mamonov wrote:
>
> | Here are several crashing instances on my build of Octave from recent
> | sources on Windows with MinGW:
> |
> | octave:1> backend('fltk');
> | octave:2> clear all;
> | octave:3> panic: Segmentation violation -- stopping myself...
> | attempting to save variables to `octave-core'...
> | save to `octave-core' complete
> | warning: figs is no longer a built-in variable; please read the NEWS
> | file or type `news' for details
>
> I checked in the following changes for this problem:
>
>  http://hg.savannah.gnu.org/hgweb/octave/rev/1500d0197484
>  http://hg.savannah.gnu.org/hgweb/octave/rev/9d4b84b14bf0
>
> | octave:1> eigs(1)
> | error: eigs: Too many eigenvalues to extract (k >= n).
> |       Use 'eig(full(A))' instead
> | terminate called after throwing an instance of 'octave_execution_exception'
> |
> | This application has requested the Runtime to terminate it in an unusual way.
> | Please contact the application's support team for more information.
> | panic: Aborted -- stopping myself...
> | attempting to save variables to `octave-core'...
> | save to `octave-core' complete
> |
> | octave:1> svds(1)
> | error: eigs: error -3 in dsaupd
> | terminate called after throwing an instance of 'octave_execution_exception'
> |
> | This application has requested the Runtime to terminate it in an unusual way.
> | Please contact the application's support team for more information.
> | panic: Aborted -- stopping myself...
> | attempting to save variables to `octave-core'...
> | save to `octave-core' complete
> | error: stdin is not a tty!
>
> I can't reproduce either of these problems.
>
> | Cases 2 and 3 might be platform-dependent issues.
>
> If you want to debug these problems, then I recommend running Octave
> under gdb and finding precisely where it is crashing.  Also, what
> version of arpack do you have?
>
> | Case 1 looks very
> | much like Octave 3.0.x clear all
> | crash that happens for certain octave-forge packages.
>
> It was a similar problem, but not exactly the same.
>
> jwe
>