From bug-octave-request  Mon Jun 21 15:03:06 1993
Subject: SIGFPE
From: A. Scottedward Hodel <Dr dot A dot Scottedward dot Hodel at eng dot auburn dot edu>
To: tiller at galois dot msfc dot nasa dot gov
Cc: Bruce dot Tenison at eng dot auburn dot edu, bug-octave,         Dr.A.Scottedward.Hodel@eng.auburn.edu
Date: Mon, 21 Jun 93 15:02:59 CDT

i am getting a clue as to why I get floating point errors in Octave.
Try the following sequence of commands:

/home/hodelas/mfiles/hodel $ octave
Octave, version 0.72.  Copyright (C) 1992, 1993, John W. Eaton.
This is free software with ABSOLUTELY NO WARRANTY.
For details, type `warranty'.

octave:1>					% type in control-c
octave:1> a = [1 2 3 4]
error: caught SIGFPE -- stopping myself...

Apparently the error trapping isn't working quite right.  On my machine,
using control-c (even during a "more") guarantees that the next non-null
command results in a SIGFPE.  I don't get this behavior on the Suns at
Auburn.

[A copy was sent to bug-octave at che dot utexas dot edu for your info]