From help-octave-request at bevo dot che dot wisc dot edu  Thu May 24 19:55:35 2001
Subject: Re: weird bug(?) on segmentation fault
From: adler at freenet dot carleton dot ca
To: "E. Joshua Rigler" <Jrigler at colorado dot edu>
cc: Help-Octave <help-octave at bevo dot che dot wisc dot edu>
Date: Thu, 24 May 2001 21:00:41 -0400 (EDT)

If you want to restore normal seg fault
behaviour, you can run a *.oct file such
as this

#include <signal.h>
#include <octave/oct.h>

DEFUN_DLD( normal_segfault, args, , "blah")
{
   signal (SIGSEGV, SIG_DFL);
   octave_value_list retval;
   return retval;
}   

This can be useful for debugging, when
you want gdb to get involved at the
point of segfault.
_______________________________________
Andy Adler,                adler at ncf dot ca

On Thu, 24 May 2001, E. Joshua Rigler wrote:
> It's nice that Octave is fairly robust, and can attempt to save a
> session even on a segmentation fault, but I'm encountering a strange
> problem.  I haven't attempted to track the cause of the seg fault
> itself, but when it occurs, octave attempts to save the session to
> "octave-core".  It does this, then doesn't exit.  This is bad, because
> then every single attempted command after that causes another seg fault,
> which then causes Octave to try to save the session...even when the
> command is "exit" or "quit".  This was an issue when I had a session
> running with several hundred MB of data, which takes quite a bit of time
> to save to disk.  Ideally there wouldn't be a seg fault, but why isn't
> Octave exitting after it saves the session?
> 
> I'm using 2.1.33.  Has anyone else esperienced something similar?
> 
> -EJR



-------------------------------------------------------------
Octave is freely available under the terms of the GNU GPL.

Octave's home on the web:  http://www.octave.org
How to fund new projects:  http://www.octave.org/funding.html
Subscription information:  http://www.octave.org/archive.html
-------------------------------------------------------------