[Pkg-octave-devel] Bug#523085: Bug#523085: octave3.0: clear -all causes segfault and coredump
On Sun, Apr 12, 2009 at 10:16:42PM +0200, Alain Baeckeroot wrote:
>
> Le 08/04/2009 à 22:41, Thomas Weber a écrit :
> >
> > On Wed, Apr 08, 2009 at 01:52:32PM +0200, Alain Bkt wrote:
> > > Package: octave3.0
> > > Version: 1:3.0.1-6lenny3
> > > Severity: important
> > >
> > >
> > > $octave
> > > octave:1> toto = 1
> > > toto = 1
> > > octave:2> clear -a
> > > panic: Segmentation fault -- stopping myself...
> > > attempting to save variables to `octave-core'...
> > > save to `octave-core' complete
> > > Erreur de segmentation
> > >
> > > The only additional package from octave forge is :
> > > octave:2> pkg list
> > > Package Name | Version | Installation directory
> > > --------------+---------+-----------------------
> > > database *| 1.0.1 | /usr/local/share/octave/site-m/database-1.0.1
> > > octave:3>
> >
> > Try unloading the package before issuing "clear all". Does this help?
> >
> > Thomas
> >
> >
> Unloading does nothing, uninstalling it solve the pb.
> I have tracked this issue a little, it seems to be in swig
> (used by the octave database package).
> I did dumb test with swig, and each time i got this issue.
>
> I have written small tools to access postgresdb, so no more need
> of this package and swig.
I'm wondering whether we should remove the packages that show these
problems from Debian. We can't do anything about it[1] and a crash is
something I can hardly tolerate?
I know that the database package is currently not packaged by us, but I
think that octave-ftp has the same problems, hasn't it?
[1] TTBOMK, it's a problem with the SWIG wrapper, isn't it?
Thomas
Reply to: