From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Ed Davison <EDavison(at)getmns(dot)com>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
Subject: | Re: FW: segfault on psycopg2 on CentOS |
Date: | 2015-03-11 14:43:54 |
Message-ID: | 550054AA.90309@aklaver.com |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | psycopg |
On 03/11/2015 07:21 AM, Ed Davison wrote:
> On 03/11/2015 07:00 AM, Ed Davison wrote:
>>> I am using Python2.7.8 and have a segfault in trying to import psycopg2.
>>>
>>> This is to get Django working with PostgreSQL.
>>>
>>> I was able to get a backtrace with gdb and here is what it is showing.
>
>> Might also help to provide some context about what you where doing when the segfault happened.
>
>> Where are you importing psycopg2 into, or is this something Django is doing?
>
>> Doing what sort of operation, if any?
>
> When I load my project to do any work on it with Django I get a segfault. When I run the Django manage.py as "python2.7 -vv manage.py" I get the following:
>
> # trying /opt/python2.7.8/lib/python2.7/site-packages/psycopg2/_psycopg.so
> dlopen("/opt/python2.7.8/lib/python2.7/site-packages/psycopg2/_psycopg.so", 2);
> Segmentation fault
>
> I have tested this with python2.7 to just simply load the psycopg2 library with the import statement and just loading the library causes a segfault as earlier stated in my backtrace.
To follow up on Danieles comment:
1) Are you running in a virtualenv?
2) Do you have more than one installation of Python?
3) More to the point what does python2.7 point to?
>
> Ed
>
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Ed Davison | 2015-03-11 14:47:42 | Re: FW: segfault on psycopg2 on CentOS |
Previous Message | Ed Davison | 2015-03-11 14:21:51 | FW: segfault on psycopg2 on CentOS |