[Numpy-discussion] crash at prompt exit after running test

[Johann Cohen-Tanugi]

thinking about it, this morning there was a fedora update to python, so 
I am using 2.6.2-4.fc12.
Looks like the problem is in python itself, hence this piece of info.
HTH,
Johann


On 03/09/2010 09:07 PM, Johann Cohen-Tanugi wrote:
> thanks Robert, here it is :
>
>   >>>  exit()
> python: Modules/gcmodule.c:277: visit_decref: Assertion `gc->gc.gc_refs
> != 0' failed.
>
> Program received signal SIGABRT, Aborted.
> 0x004a1416 in __kernel_vsyscall ()
> Missing separate debuginfos, use: debuginfo-install
> atlas-3.8.3-12.fc12.i686 compat-libf2c-34-3.4.6-18.i686
> keyutils-libs-1.2-6.fc12.i686 krb5-libs-1.7.1-2.fc12.i686
> libcom_err-1.41.9-7.fc12.i686 libgcc-4.4.3-4.fc12.i686
> libgfortran-4.4.3-4.fc12.i686 libselinux-2.0.90-5.fc12.i686
> (gdb) bt
> #0  0x004a1416 in __kernel_vsyscall ()
> #1  0x00609a91 in raise (sig=6) at
> ../nptl/sysdeps/unix/sysv/linux/raise.c:64
> #2  0x0060b35a in abort () at abort.c:92
> #3  0x00602be8 in __assert_fail (assertion=<value optimized out>,
> file=<value optimized out>, line=<value optimized out>, function=<value
> optimized out>)
>       at assert.c:81
> #4  0x0032e31e in visit_decref (op=<value optimized out>, data=<value
> optimized out>) at Modules/gcmodule.c:277
> #5  0x002a18c2 in dict_traverse (op=<value optimized out>, visit=<value
> optimized out>, arg=<value optimized out>) at Objects/dictobject.c:2003
> #6  0x0032eaf3 in subtract_refs (generation=<value optimized out>) at
> Modules/gcmodule.c:296
> #7  collect (generation=<value optimized out>) at Modules/gcmodule.c:817
> #8  0x0032f640 in PyGC_Collect () at Modules/gcmodule.c:1292
> #9  0x003200f0 in Py_Finalize () at Python/pythonrun.c:424
> #10 0x00320218 in Py_Exit (sts=<value optimized out>) at
> Python/pythonrun.c:1714
> #11 0x00320367 in handle_system_exit () at Python/pythonrun.c:1116
> #12 0x0032057d in PyErr_PrintEx (set_sys_last_vars=<value optimized
> out>) at Python/pythonrun.c:1126
> #13 0x0032079f in PyErr_Print () at Python/pythonrun.c:1035
> #14 0x00320f9a in PyRun_InteractiveOneFlags (fp=<value optimized out>,
> filename=<value optimized out>, flags=<value optimized out>) at
> Python/pythonrun.c:843
> #15 0x00321093 in PyRun_InteractiveLoopFlags (fp=<value optimized out>,
> filename=<value optimized out>, flags=0xbfffefec) at Python/pythonrun.c:760
> #16 0x003211df in PyRun_AnyFileExFlags (fp=<value optimized out>,
> filename=0x365add "<stdin>", closeit=<value optimized out>, flags=<value
> optimized out>)
>       at Python/pythonrun.c:729
> #17 0x0032dc85 in Py_Main (argc=<value optimized out>, argv=<value
> optimized out>) at Modules/main.c:599
> #18 0x080485c8 in main (argc=<value optimized out>, argv=<value
> optimized out>) at Modules/python.c:23
>
>
> I also saw things like:
> warning: .dynamic section for "/lib/libcom_err.so.2" is not at the
> expected address
> warning: difference appears to be caused by prelink, adjusting expectations
> warning: .dynamic section for "/lib/libkeyutils.so.1" is not at the
> expected address
> warning: difference appears to be caused by prelink, adjusting expectations
>
> Johann
>
> On 03/09/2010 08:56 PM, Robert Kern wrote:
>    
>> On Tue, Mar 9, 2010 at 13:50, Johann Cohen-Tanugi<cohen at lpta.in2p3.fr>   wrote:
>>
>>      
>>> I have tried to localize the core dump in vain.... any idea where I should
>>> look for it?
>>> I did not manage to catch it with pdb :
>>>
>>>        
>> Not pdb, gdb.
>>
>> $ gdb python
>> ...
>> (gdb) run
>> Starting program ...
>> ... # Possibly another (gdb) prompt:
>> (gdb) continue  #<- Type this.
>> Python 2.6.2 ...
>>
>>
>>      
>>>>> import numpy  #<- Type this and do whatever else is necessary to reproduce the crash.
>>>>>
>>>>>            
>> ...
>> (gdb) bt  #<- Type this.
>> .... #<- Copy-paste these results here.
>>
>>
>>      
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discussion at scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion
>
>