#7764: [gis] Segfault on 
django.contrib.gis.geos.prototypes.errcheck.check_string
--------------------------------------+-------------------------------------
          Reporter:  santiago_aguiar  |         Owner:  jbronn                 
            Status:  closed           |     Milestone:                         
         Component:  GIS              |       Version:  gis                    
        Resolution:  worksforme       |      Keywords:  segfault geos string_at
             Stage:  Accepted         |     Has_patch:  1                      
        Needs_docs:  1                |   Needs_tests:  0                      
Needs_better_patch:  1                |  
--------------------------------------+-------------------------------------
Changes (by jbronn):

  * status:  new => closed
  * resolution:  => worksforme

Comment:

 Works for me.  I've tried my hardest and cannot reproduce this bug.

 I've created a VM that is running CentOS 5.2.  The following packages are
 installed:

 Binary: Python 2.4.3, Apache 2.2.3, mod_python 3.2.8, PostgreSQL 8.1,
 [http://dag.wieers.com/rpm/packages/python-ctypes/ ctypes 1.0.0]

 Source: GEOS 3.0.0, PROJ.4 4.6.0, GDAL 1.5.2, psycopg 2.0.7, PostGIS 1.3.2

 All GEOS and GDAL model tests pass; the entire
 [browser:django/branches/gis/django/contrib/gis/tests GeoDjango test suite
 passes].  Moreover, I installed my [http://geodjango.org/hg/where2
 project] used for the tutorial at Where 2.0.  The `where2` project has 68K
 `PointField` models (`tabc.Location`), 8.8K of `MultiLineString`
 (`harris.Edge`) models, and 58K `MultiPolygon` (`census.State`,
 `census.County`, `texas.Neighborhood`, and `texas.Zip`).  All data
 imported fine and views worked as expected with no segmentation faults
 encountered.  Finally, I was able to view ''and'' edit all models in the
 geographic admin (available in SVN since this morning).  Both admin and
 views were served up via Apache/mod_python.

 I had a lot of difficulty getting Apache/mod_python working.
 Specifically, Apache wouldn't couldn't find the project settings file
 despite a globally set `PYTHONPATH`, correct permissions, and a correctly
 set `PythonPath` directive in httpd.conf -- however, no segfaults.  After
 I disabled SELinux, it was smooth sailing -- could this be your problem?

 Unless I'm provided with a reproducible test case, this ticket is closed.

-- 
Ticket URL: <http://code.djangoproject.com/ticket/7764#comment:7>
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to