Opened 16 years ago
Last modified 16 years ago
#2770 closed defect
GDAL breaks mapscript + psycopg — at Initial Version
| Reported by: | hbarrett | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | default | Version: | unspecified |
| Severity: | major | Keywords: | |
| Cc: |
Description
I upgraded GDAL from 1.4.1 to 1.6.0. Immediately after the install I checked the site that uses GDAL via mapscript and the html was not being generated fully. I tracked the problem down to the psycopg connection declaration. I created a new test script an found that psycopg works alone and mapserver works alone, but when I import mapscript and psycopg, the psycopg connection declaration fails with a Segmentation fault.
The only reason I am submitting this as a GDAL bug is the only thing that has changed is GDAL.
This is the result of running the test script with gdb python.
Starting program: /usr/bin/python2.3 test.py (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1208088896 (LWP 16537)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found)
Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1208088896 (LWP 16537)] 0x00330469 in SSL_pending () from /lib/libssl.so.4
