#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: Accepted | Has_patch: 1
Needs_docs: 1 | Needs_tests: 0
Needs_better_patch: 1 |
--------------------------------------+-------------------------------------
Changes (by jbronn):
* needs_better_patch: 0 => 1
* needs_docs: 0 => 1
* milestone: 1.0 beta =>
Comment:
Can you provide the situation in which the segmentation fault occurs? An
example case would be nice, or the steps used to reproduce would be nice
(e.g., does this happen every time, or randomly, on startup, etc.?).
This patch introduces a serious memory leak and will not be applied in its
current form. There were reasons why the `c_char_p` type wasn't
specified (as noted in the comments) because, IIRC, it made it difficult
to free the memory allocated in the GEOS library with `libc.free`. I'll
re-research into whether it's possible to specify the response type and be
able to free the memory address.
Ticket triagers: please let the branch maintainers handle the setting of
milestones and tickets for version 1.0.
--
Ticket URL: <http://code.djangoproject.com/ticket/7764#comment:3>
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
-~----------~----~----~----~------~----~------~--~---
