Several crash cases for build with recent sources

Tatsuro MATSUOKA tmacchant at yahoo.co.jp
Wed May 20 22:21:13 CDT 2009


Hello

To my memory, Benjamin had done some works for development sources.
However I do not know how recent he followed in the development branch.

Regards

Tatsuro 

--- Tatsuro MATSUOKA wrote:

> Hello
> 
> I have not yet tested recent development branch of sources.
> I am now testing the latest octave-forge package on 3.0.5.
> 
> The test for development branch will be done after octave-forge package tests will be finished.
> 
> Regards
> 
> Tatsuro
> 
> --- Alexander Mamonov  wrote:
> 
> > As I mentioned before, I believe that the core dumps are an issue of
> > how MinGW GCC deals with exceptions thrown across the boundaries of
> > dynamically linked modules. Can somebody with a MinGW build of current
> > sources reproduce these crashes? Tatsuro? Michael?
> > 
> > Regards,
> > Alex
> > 
> > On Wed, May 20, 2009 at 8:50 AM, Jaroslav Hajek <highegg at gmail.com> wrote:
> > > On Tue, May 12, 2009 at 12:47 AM, Alexander Mamonov <mamonov at gmail.com> 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
> > >>
> > >>
> >
>
--------------------------------------------------------------------------------------------------------------------------------------------------------------
> > >>
> > >> 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!
> > >>
> > >>
> >
>
--------------------------------------------------------------------------------------------------------------------------------------------------------------
> > >>
> > >> Cases 2 and 3 might be platform-dependent issues. Case 1 looks very
> > >> much like Octave 3.0.x clear all
> > >> crash that happens for certain octave-forge packages.
> > >>
> > >
> > > I can confirm 2 and 3 generate error messages and I'm working on a
> > > patch that improves things a bit (in particular the dsaupd). However,
> > > I see no core dumps.
> > >
> > >
> > >
> > > --
> > > RNDr. Jaroslav Hajek
> > > computing expert & GNU Octave developer
> > > Aeronautical Research and Test Institute (VZLU)
> > > Prague, Czech Republic
> > > url: www.highegg.matfyz.cz
> > >
> > 
> 
> 
> --------------------------------------
> Power up the Internet with Yahoo! Toolbar.
> http://pr.mail.yahoo.co.jp/toolbar/
> 


--------------------------------------
Power up the Internet with Yahoo! Toolbar.
http://pr.mail.yahoo.co.jp/toolbar/


More information about the Bug-octave mailing list