Octave crashes with libatlas
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octave3.2 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: octave3.2
With libatlas3gf-base installed, even a simple dot product produces crash; e.g.:
a=[1 2 3]; a*a'
results in:
panic: Illegal instruction -- stopping myself...
attempting to save variables to `octave-core'...
save to `octave-core' complete
Illegal instruction
CPUinfo (in case it is needed):
processor : 0
vendor_id : AuthenticAMD
cpu family : 6
model : 10
model name : AMD Athlon(tm) XP 2800+
stepping : 0
cpu MHz : 2087.500
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 1
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca cmov pat pse36 mmx fxsr sse syscall mmxext 3dnowext 3dnow up
bogomips : 4184.22
clflush size : 32
cache_alignment : 32
address sizes : 34 bits physical, 32 bits virtual
power management: ts
Ubuntu version: 11.04
Package version (sorry for hungarian words):
Installed: 3.2.4-8
Jelölt: 3.2.4-8
Version table:
*** 3.2.4-8 0
500 http://
100 /var/lib/
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: octave3.2 3.2.4-8
ProcVersionSign
Uname: Linux 2.6.38-8-generic i686
NonfreeKernelMo
Architecture: i386
Date: Wed May 11 10:08:28 2011
ProcEnviron:
LANGUAGE=hu_HU:en
LANG=hu_HU.UTF-8
SHELL=/bin/bash
SourcePackage: octave3.2
UpgradeStatus: Upgraded to natty on 2011-05-09 (1 days ago)
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test it on a currently supported Ubuntu version. When you test it and it is still an issue, kindly upload the updated logs by running apport-collect 780966 and any other logs that are relevant for this particular issue.