Account Options

  1. Sign in
The old Google Groups will be going away soon.
Switch to the new Google Groups.
Google Groups Home
« Groups Home
Message from discussion GeoDjango in Ubuntu 8.10, Segmentation Fault
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
GRoby  
View profile  
 More options Dec 2 2008, 8:32 pm
From: GRoby <gregory.r...@gmail.com>
Date: Tue, 2 Dec 2008 17:32:36 -0800 (PST)
Local: Tues, Dec 2 2008 8:32 pm
Subject: Re: GeoDjango in Ubuntu 8.10, Segmentation Fault
I can confirm that all of my seg faults were all on my 64 bit machine
but could not be duplicated when I tried to on my 32 bit test virtual
machines.

On Dec 2, 7:40 pm, rcoup <robert.c...@gmail.com> wrote:

> 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 explicitly marking argument and
> return types. "

> Looking back through the modwsgi thread and this one, everyone's on
> 64bit, except the CentOS guy who said it worked ok on 32bit but not on
> 64bit.

> Maybe thats the problem with the ctypes+geos bindings in GeoDjango?
> I'm running something-pre-1.0, but I can try it on a trunk checkount
> to confirm the same symptoms.

> Rob :)


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.