#7764: [gis] Segfault on
django.contrib.gis.geos.prototypes.errcheck.check_string
---------------------------------------------+------------------------------
Reporter: santiago_aguiar | Owner: nobody
Status: new | Milestone:
Component: GIS | Version: gis
Resolution: | Keywords: segfault geos
string_at
Stage: Design decision needed | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 1 |
---------------------------------------------+------------------------------
Comment (by anonymous):
Replying to [comment:4 jbronn]:
> Are you running Apache in threaded mode? The GEOS library is not thread
safe -- I have a hunch this may be the problem.
The referred ticket also suggested this option, and also pointer to a
ctypes bug. However, I tracked the issue running httpd -X so I could check
where the segfault was happening, and in that case I'm running only one
worker... I don't see how a threading issue could be the cause here.
It happened always, at the same spot, after performing a SELECT from the
DB and trying to render the geom as a string (a POINT in this case). I
tracked the issue using the admin interface (tying to avoid problems
specific to my app views, in which the problem also appeared) and gdb. I'm
going to see if I can put some more time in this and I'll report back.
The guys at gispython implemented another approach, which I didn't like
much.
I'm running python 2.4 with ctypes 1.0.0.
--
Ticket URL: <http://code.djangoproject.com/ticket/7764#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
