Re: GNU Octave 3.6.3 Released

[Philip Nienhuis]

Jordi Gutiérrez Hermoso-2 wrote
> 
> On 5 September 2012 15:52, Sergei Steshenko <sergstesh@> wrote:
> 
> <snipped>
> 
> If that's your source directory and you built in-source there should
> be a "run-octave" script in it along with test/fntests.m. If so,
> please do
> 
>     ./run-octave -g --norc --silent --no-history test/fntests.m
> 
> This will put you in a gdb session. Do "run" to run the test suite.
> This will run slower than normal because it'll be running in a
> debugger. When Octave crashes, you should be dumped back to gdb. Do
> "bt" to get the stack trace.
> 
> This isn't exactly one-button, but it's about as simple as it gets.
> 

Continuing on my earlier post, along those (debug) lines I get (on Mageia 2)

octave:1> which pcg.m
`pcg.m' is the file
/home/philip/devel/oct363/../octave-3.6.3/scripts/sparse/pcg.m
octave:2> test pcg.m

Program received signal SIGILL, Illegal instruction.
0xb4576acd in ATL_dJIK36x36x36TN36x36x0_a1_b0 () from
/usr/lib/atlas-sse3/libatlas.so.3
(gdb) bt
#0  0xb4576acd in ATL_dJIK36x36x36TN36x36x0_a1_b0 () from
/usr/lib/atlas-sse3/libatlas.so.3
#1  0x0000007b in ?? ()
#2  0x083474a0 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
(gdb) 

... so I guess it is indeed Mageia that is at fault. 
(And I also see why: my Pentium-M laptop's CPU has no SSE3. Apparently
Mageia's CPU detection at install time has a hick-up).

Thanks Jordi, that was a very helpful hint!

Philip



--
View this message in context: 
http://octave.1599824.n4.nabble.com/GNU-Octave-3-6-3-Released-tp4643700p4643769.html
Sent from the Octave - General mailing list archive at Nabble.com.