horribly slimy segault c-extension

[Juha Autero]

"Hunter Peress" <dsada at asd.com> writes:

> On the right we see the results of "gdb python core"  
>
> since i dont see "test" anywhere, and since theres "??"  im lead to
> believe that maybe i didnt load the core file correctly? or maybe i have
> not set some name properly in the C? 

It looks more like PyCFunction_Call gets a corrupted function pointer.
Because of address 0x00000009 I'd guess that it's NULL pointer, but
since the next stack frame may be corrupted, I wouldn't rely on that.

-- 
Juha Autero
http://www.iki.fi/jautero/
Eschew obscurity!