I am using an ATLAS 64 bit lapack 3.9.1. My cpu (4 cpus) ------------------------------------------------- processor : 0 vendor_id : GenuineIntel cpu family : 6 model : 23 model name : Intel(R) Xeon(R) CPU X5460 @ 3.16GHz stepping : 6 cpu MHz : 3158.790 cache size : 6144 KB physical id : 0 siblings : 4 core id : 0 cpu cores : 4 fpu : yes fpu_exception : yes cpuid level : 10 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall nx lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm bogomips : 6321.80 clflush size : 64 cache_alignment : 64 address sizes : 38 bits physical, 48 bits virtual power management: ----------------------------------------------------------- A system trace ends with futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 write(2, ".", 1) = 1 2655 futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 futex(0xc600bb0, FUTEX_WAKE, 1) = 0 2655 --- SIGSEGV (Segmentation fault) @ 0 (0) --- 2655 +++ killed by SIGSEGV +++ ---------------------------------------- I get no core file Robert Kern wrote:
On Tue, Jul 29, 2008 at 14:16, James Turner <jturner@gemini.edu> wrote:
I have built NumPy 1.1.0 on RedHat Enterprise 3 (Linux 2.4.21 with gcc 3.2.3 and glibc 2.3.2) and Python 2.5.1. When I run numpy.test() I get a core dump, as follows. I haven't noticed any special errors during the build. Should I post the entire terminal output from "python setup.py install"? Maybe as an attachment? Let me know if I can provide any more info.
Can you do
numpy.test(verbosity=2)
? That will print out the name of the test before running it, so we will know exactly which test caused the core dump.
A gdb backtrace would also help.