[capi-sig] Segfault when using own C-written module and exiting python

Laurent Gautier lgautier at gmail.com
Fri Jun 6 21:40:49 CEST 2008

I have probably found the problem. I report it here in case someone
has the same issue later.

In my tp_new I had:

PyObject_New(MyType, type);

(and it was working just fine until I started with subclasses)

while it seems that it should have been:

type->tp_alloc(type, 0);


2008/6/6 Laurent Gautier <lgautier at gmail.com>:
> Dear List,
> I am having trouble with some of the use-cases for a C-written module of my own
> (if curious, I am working on Python-R interface... this is open source so I can
> provide the whole source if needed).
> Everything is working just fine and as expected... until the python
> process exits.
> When running my test script through gdb and with the '-v' flag for
> Python, it ends with
> ---
> # cleanup __main__
> Program received signal SIGSEGV, Segmentation fault.
> [Switching to Thread 0xb7dde8c0 (LWP 19670)]
> 0x080f3d08 in PyObject_GC_UnTrack ()
> ---
> I have looked for information on the internet... but have not found
> much. Would this kind
> of error be familiar to anyone ?
> Thanks,
> Laurent

More information about the capi-sig mailing list