Re: psycopg2 2.0.8 - segmentation fault
"Gangadharan S.A." <[email protected]>
| Newsgroups | gmane.comp.python.db.psycopg.devel |
|---|---|
| Message-ID | <[email protected]> |
2009/3/25 Federico Di Gregorio <fog-NGVKUo/i/[email protected]> > > Program received signal SIGABRT, Aborted. > > [Switching to Thread 1283557696 (LWP 12437)] > > 0x00002b2fdc478535 in raise () from /lib64/libc.so.6 > > (gdb) bt > > #0 0x00002b2fdc478535 in raise () from /lib64/libc.so.6 > > #1 0x00002b2fdc479990 in abort () from /lib64/libc.so.6 > > #2 0x00002b2fdc4af6db in __libc_message () from /lib64/libc.so.6 > > #3 0x00002b2fdc4b48fe in malloc_printerr () from /lib64/libc.so.6 > > #4 0x00002b2fdc4b5f36 in free () from /lib64/libc.so.6 > > #5 0x00002b2fe062f7e7 in connection_dealloc (obj=0x2aaaaac0ef30) at > > psycopg/connection_type.c:464 > > Mm.. very strange. Are you sharing the connection among different > threads? > > Yes, at a couple of places. But it is protected by locks. _______________________________________________ Psycopg mailing list Psycopg-IAPFreCvJWPBWskQ1e/[email protected] http://lists.initd.org/mailman/listinfo/psycopg