[Numpy-discussion] Numpy Segmentation Fault

Yogesh Tomar ytomar@gmail....
Tue Apr 6 06:28:53 CDT 2010


numpy 1.3.0 also segfaults the same way.
Is it the problem with libc library?

Gdb stacktrace.



gdb) run /home/eqan/64bit/current/segf.py
Starting program: /home/eqan/tapas/64bit/Python/2.6.4_x641/bin/python
/home/eqan/64bit/current/segf.py
[Thread debugging using libthread_db enabled]
[New Thread 47653213733440 (LWP 24970)]
0 -------------------------------
1 -------------------------------
2 -------------------------------
3 -------------------------------
4 -------------------------------
5 -------------------------------
6 -------------------------------
7 -------------------------------
8 -------------------------------
9 -------------------------------
here

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 47653213733440 (LWP 24970)]
0x00000034d8c71033 in _int_free () from /lib64/libc.so.6
(gdb) up
#1  0x00000034d8c74c5c in free () from /lib64/libc.so.6
(gdb) up
#2  0x00002b57203451db in code_dealloc (co=0xdab63f0) at
Objects/codeobject.c:260
260             Py_XDECREF(co->co_code);
(gdb) up
#3  0x00002b5720359a73 in func_dealloc (op=0xdab67d0) at
Objects/funcobject.c:454
454             Py_DECREF(op->func_code);
(gdb) up
#4  0x00002b57203691ed in insertdict (mp=0xda8ae90, key=0xda2f180,
hash=1904558708720393281, value=0x2b572066c210) at Objects/dictobject.c:459
459                     Py_DECREF(old_value); /* which **CAN** re-enter */
(gdb) up
#5  0x00002b572036b153 in PyDict_SetItem (op=0xda8ae90, key=0xda2f180,
value=0x2b572066c210) at Objects/dictobject.c:701
701             if (insertdict(mp, key, hash, value) != 0)
(gdb) up
#6  0x00002b572036d5c8 in _PyModule_Clear (m=<value optimized out>) at
Objects/moduleobject.c:138
138                                     PyDict_SetItem(d, key, Py_None);
(gdb) up
#7  0x00002b57203dfa34 in PyImport_Cleanup () at Python/import.c:474
474                                     _PyModule_Clear(value);
(gdb) up
#8  0x00002b57203ed167 in Py_Finalize () at Python/pythonrun.c:434
434             PyImport_Cleanup();
(gdb) up
#9  0x00002b57203f9cdc in Py_Main (argc=<value optimized out>,
argv=0x7fff8a7bf478) at Modules/main.c:625
625             Py_Finalize();
(gdb) up
#10 0x00000034d8c1d8b4 in __libc_start_main () from /lib64/libc.so.6
(gdb) up

Regards,
Yogesh Tomar


On Tue, Apr 6, 2010 at 4:22 PM, David Cournapeau <cournape@gmail.com> wrote:

> On Tue, Apr 6, 2010 at 7:46 PM, Yogesh Tomar <yogesh.tomar@gmail.com>
> wrote:
> >
> > Hi all,
> >
> > I am getting numpy segmentation fault on a custom install of python to a
> > prefix.
>
> What happens if you build numpy 1.3.0 against python 2.6.1 (instead of
> your own 2.6.4) ? For numpy, a strace is not really useful (a
> backtrace from gdb much more),
>
> cheers,
>
> David
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.scipy.org/pipermail/numpy-discussion/attachments/20100406/92908625/attachment.html 


More information about the NumPy-Discussion mailing list