Re: GeoDjango in Ubuntu 8.10, Segmentation Fault

2008-12-03 Thread rcoup
Hi, On Dec 3, 5:21 pm, Andre P LeBlanc <[EMAIL PROTECTED]> wrote: > Confirmed also. only happens on my 64-bit machine, and is not related > to apache at all as I can reproduce it faithfully in ipython. > I tried pretty hard to replicate it in the console and couldn't - none of our unit tests cra

Re: GeoDjango in Ubuntu 8.10, Segmentation Fault

2008-12-02 Thread rcoup
On Dec 3, 1:40 pm, rcoup <[EMAIL PROTECTED]> wrote: > Leading me to:http://sgillies.net/blog/829/shapely-1-0-8/ > > "The same problem [segfault] could afflict any python package that > uses Ctypes on 64-bit systems without explicitly marking argument and > return types.

Re: GeoDjango in Ubuntu 8.10, Segmentation Fault

2008-12-02 Thread rcoup
Posting to geos-devel, I got this reply from Paul Ramsey: http://lists.osgeo.org/pipermail/geos-devel/2008-December/003800.html Leading me to: http://sgillies.net/blog/829/shapely-1-0-8/ "The same problem [segfault] could afflict any python package that uses Ctypes on 64-bit systems without expl

Re: GeoDjango in Ubuntu 8.10, Segmentation Fault

2008-12-02 Thread rcoup
On Nov 26, 6:07 am, Justin Bronn <[EMAIL PROTECTED]> wrote: > I created an Ubuntu 8.10 VM to try and test out this problem. > However, the only way that I could reproduce your exact problem > (segfault upon HTTP request) is when using the mpm-worker (threaded) > Apache.  When using the prefork,