[capi-sig] Segfault when using own C-written module and exiting python
mal at egenix.com
Fri Jun 6 13:04:40 CEST 2008
On 2008-06-06 12:31, Laurent Gautier wrote:
> 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 ?
I've never seen this particular error before, but it's likely that you
have a ref count bug somewhere in your code.
Professional Python Services directly from the Source (#1, Jun 06 2008)
>>> Python/Zope Consulting and Support ... http://www.egenix.com/
>>> mxODBC.Zope.Database.Adapter ... http://zope.egenix.com/
>>> mxODBC, mxDateTime, mxTextTools ... http://python.egenix.com/
2008-07-07: EuroPython 2008, Vilnius, Lithuania 30 days to go
:::: Try mxODBC.Zope.DA for Windows,Linux,Solaris,MacOSX for free ! ::::
eGenix.com Software, Skills and Services GmbH Pastor-Loeh-Str.48
D-40764 Langenfeld, Germany. CEO Dipl.-Math. Marc-Andre Lemburg
Registered at Amtsgericht Duesseldorf: HRB 46611
More information about the capi-sig