capi-sig June 2008

capi-sig@python.org

4 participants
3 discussions

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

by Laurent Gautier

2008/6/7 Stefan Behnel <stefan_ml(a)behnel.de>: > Hi, > > laurent wrote: >> On Fri, 2008-06-06 at 13:23 +0200, Stefan Behnel wrote: >>> If the existing code base isn't too large yet, consider switching to Cython >>> instead of C. >> >> The C part is only a little more than 2000 lines of source so far >> (and with no plan to go much beyond that, it's about feature-complete >> for a first release). > > This might be a good read then: > > http://permalink.gmane.org/gmane.comp.python.cython.devel/1965 > > >> The CPython project looks very nice. > > Cython. CPython is the name commonly used for the standard Python implementation. > Yes. It was just a freudian slip, I suppose. >> However, there are potentially dark corners I have to work around (and >> so far I am not completely successful at it, as my post suggests > > Then you should really consider letting Cython give you a hand with the ugly > things (like garbage collection or class definition), so that you can > concentrate on the more interesting stuff. Yes, I have read the mailing reference in the beginning of your mail... and I'll stick to C given the nature of what I have to do (especially since this is now working ;-) ). > Stefan > >

12 years, 11 months

Segfault when using own C-written module and exiting python

by Laurent Gautier

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

12 years, 11 months

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

by Stefan Behnel

Hi, laurent wrote: > On Fri, 2008-06-06 at 13:23 +0200, Stefan Behnel wrote: >> If the existing code base isn't too large yet, consider switching to Cython >> instead of C. > > The C part is only a little more than 2000 lines of source so far > (and with no plan to go much beyond that, it's about feature-complete > for a first release). This might be a good read then: http://permalink.gmane.org/gmane.comp.python.cython.devel/1965 > The CPython project looks very nice. Cython. CPython is the name commonly used for the standard Python implementation. > However, there are potentially dark corners I have to work around (and > so far I am not completely successful at it, as my post suggests Then you should really consider letting Cython give you a hand with the ugly things (like garbage collection or class definition), so that you can concentrate on the more interesting stuff. Stefan

12 years, 11 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

capi-sig June 2008