[Pkg-octave-devel] Bug#340320: marked as forwarded (octave2.1-headers: mkoctfile generated functions crash randomly)

Tue Nov 22 21:03:17 UTC 2005

Your message dated Tue, 22 Nov 2005 21:37:04 +0100
with message-id <20051122203704.GA17750 at laboiss2>
has caused the Debian Bug report #340320,
regarding octave2.1-headers: mkoctfile generated functions crash randomly
to be marked as having been forwarded to the upstream software
author(s) help at octave.org.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

---------------------------------------
Received: (at 340320-forwarded) by bugs.debian.org; 22 Nov 2005 20:37:15 +0000
>From laboissiere at cbs.mpg.de Tue Nov 22 12:37:15 2005
Return-path: <laboissiere at cbs.mpg.de>
Received: from kom.psy.mpg.de ([192.129.1.23] helo=kom.mpipf-muenchen.mpg.de)
	by spohr.debian.org with esmtp (Exim 4.50)
	id 1Eeet8-0001XX-RI
	for 340320-forwarded at bugs.debian.org; Tue, 22 Nov 2005 12:37:15 -0800
Received: from amalie.intra.mpipf-muenchen.mpg.de ([10.1.1.2])
	by kom.mpipf-muenchen.mpg.de with esmtp (Exim 4.34)
	id 1Eeesz-00085S-AQ; Tue, 22 Nov 2005 21:37:05 +0100
Received: from [10.80.1.253] (helo=laboiss2)
	by amalie.intra.mpipf-muenchen.mpg.de with esmtp (Exim 4.05)
	id 1Eeesz-0001Ak-00; Tue, 22 Nov 2005 21:37:05 +0100
Received: from rafael by laboiss2 with local (Exim 3.36 #1 (Debian))
	id 1Eeesy-0004ff-00; Tue, 22 Nov 2005 21:37:04 +0100
Date: Tue, 22 Nov 2005 21:37:04 +0100
From: Rafael Laboissiere <rafael at debian.org>
To: help at octave.org
Cc: Teemu Ikonen <tpikonen at pcu.helsinki.fi>,
	340320-forwarded at bugs.debian.org
Subject: Re: octave2.1-headers: mkoctfile generated functions crash randomly
Message-ID: <20051122203704.GA17750 at laboiss2>
References: <200511221734.jAMHYsSO024104 at sender-01.it.helsinki.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200511221734.jAMHYsSO024104 at sender-01.it.helsinki.fi>
Organization: Debian GNU/Linux
User-Agent: Mutt/1.5.9i
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
	(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no 
	version=2.60-bugs.debian.org_2005_01_02

Below is a bug report filed against the octave2.1-headers Debian package
(http://bugs.debian.org/340320).  See my comments after the included
message.

* Teemu Ikonen <tpikonen at pcu.helsinki.fi> [2005-11-22 19:34]:

> Package: octave2.1-headers
> Version: 2.1.72-4
> Severity: normal
> 
> Oct-functions generated by mkoctfile segfault randomly, but very often. For
> example, the following innocent-looking function:
> 
> -*-*-*-
> 
> #include <octave/oct.h>
> 
> DEFUN_DLD(uitest, args, , " ")
> {
>       int x = 20;
>       int y = 20;
> 	    
>       return octave_value(Matrix(y,x));
> 		  
> }
> 		  
> -*-*-*-
> 
> produces this when ran repeatedly:
> 
> octave:1> uitest();
> octave:2> uitest();
> octave:3> uitest();
> octave:4> uitest();
> panic: Segmentation fault -- stopping myself...
> attempting to save variables to octave-core'...
> save to octave-core' complete
> Segmentation fault
> 
> I can usually make Octave crash by running uitest less than 10 times.
> 
> Since I run a mixed system of testing and unstable, I'm rather certain that
> the crashes are caused by some kind of library version mismatch which the
> dependencies do not take into account. Octave 2.1.69 from sarge does not
> crash with the test above.
> 
> I would appreciate any ideas on how to get oct-files working again.

I confirm the problem here in my sid chroot.  Your program crashes in a
systematic way producing the following:

$ echo 'for i=1:100;printf("%i.",i);fflush(stdout);uitest();end' | octave -qf
1.2.3.4.5.6.7.8.9.panic: Segmentation fault -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Segmentation fault

What puzzles me is that it works fine in my etch (testing) system.  It looks
like a library problem.

How should I proceed in order to find where the bug comes from?

-- 
Rafael