Segmentation fault in PyObjectMalloc on FreeBSD

2008-12-19 Thread youcancallmeal
I have a multithreaded python app running on FreeBSD (both 7.0 and 6.3) that crashes with a segmentation fault coming from PyObjectMalloc. This first happened using Python 2.5 built from Ports. I then pulled down r261 from Subversion and built that so I would have debugging symbols; it still crashe

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread YouCanCallMeAl
On Oct 22, 8:11 am, "Jesse Noller" <[EMAIL PROTECTED]> wrote: > On Tue, Oct 21, 2008 at 6:45 PM,  <[EMAIL PROTECTED]> wrote: > > It seems that the multiprocessing module in 2.6 is broken for *BSD; > > I've seen issue 3770 regarding this. I'm curious if there are more > > details on this issue since

Re: Python 2.6, multiprocessing module and BSD

2008-10-22 Thread YouCanCallMeAl
On Oct 21, 8:08 pm, Philip Semanchuk <[EMAIL PROTECTED]> wrote: > On Oct 21, 2008, at 6:45 PM, [EMAIL PROTECTED] wrote: > > > It seems that the multiprocessing module in 2.6 is broken for *BSD; > > I've seen issue 3770 regarding this. I'm curious if there are more > > details on this issue since th

Python 2.6, multiprocessing module and BSD

2008-10-21 Thread YouCanCallMeAl
It seems that the multiprocessing module in 2.6 is broken for *BSD; I've seen issue 3770 regarding this. I'm curious if there are more details on this issue since the posts in 3770 were a bit unclear. For example, one post claimed that the problem was that sem_open isn't implemented in *BSD, but it