release 3.2.1

[Riccardo Corradini]

% program bug.m

clear all;
k=70
rm = rand(k,k);
im = i*rand(k,k);
M =[rm+im];

eig(M) 

These are the results with octave3.0.5
octave:2> bug
 ** On entry to ZGEEV  parameter number  5 had an illegal value
k =  70
error: exception encountered in Fortran subroutine zgeev_
error: unrecoverable error in zgeev
error: near line 9 of file `/home/corradin/octbenchmark/bug.m'

These are the results with octave3.2.0
octave:2> bug
panic: Segmentation fault -- stopping myself...
k =  70
attempting to save variables to `octave-core'...
save to `octave-core' complete
Segmentation fault

I think that octave3.2.0 should give the same results of octave3.0.5. 
Hope this helps to show the bug.
Thanks in advance
Bests
Riccardo Corradini

--- Mer 15/7/09, John W. Eaton <jwe at octave.org> ha scritto:

Da: John W. Eaton <jwe at octave.org>
Oggetto: Re: release 3.2.1
A: "Riccardo Corradini" <riccardocorradini at yahoo.it>
Cc: bug at octave.org
Data: Mercoledì 15 luglio 2009, 20:33

On  7-Jul-2009, Riccardo Corradini wrote:

| Dear staff,

| I may confirm that the bug doesn't persist on octave 3.2.x using
| lapack 3.1..1 and linking multithread ATLAS 3.8.2 and suitesparse
| 3.4.0 etc..with this version 3.1.1.

I'm confused now.  Does this mean that you claim the bug is fixed,
there is not really a bug, the bug is in ATLAS instead of Octave, or
what?

Also, there is really no need to post your message to all three of the
Octave lists.  Please pick the single most appropriate list.

jwe



      
-------------- next part --------------
An HTML attachment was scrubbed...
URL: https://www-old.cae.wisc.edu/pipermail/bug-octave/attachments/20090716/6cb1c075/attachment-0001.html