On Wed, 2001-09-19 at 18:59, Mayers, Philip J wrote:
I'm still seeing periodic/sporadic crashes of my Zope installation, and it's getting *REALLY* annoying :o)
I sometimes get a core file (if I'm lucky) whose backtrace normally reads:
Program terminated with signal 11, Segmentation fault. <snip> #0 0x401364fe in __select () from /lib/libc.so.6 (gdb) bt #0 0x401364fe in __select () from /lib/libc.so.6 #1 0x4031708c in __DTOR_END__ () from /usr/lib/libpq.so.2 #2 0x4030ecad in PQgetResult () from /usr/lib/libpq.so.2 #3 0x4030ee1c in PQexec () from /usr/lib/libpq.so.2 #4 0x402f9acb in curs_switch_autocommit () from /usr/lib/python2.1/site-packages/psycopgmodule.so #5 0x402fa0e8 in curs_switch_autocommit () from /usr/lib/python2.1/site-packages/psycopgmodule.so
this is _strange_ because ZPsycopgDA *does* *not* support autocommit and there is no way to enable it while using psycopg with Zope. [snip]
#32 0x8058aef in PyEval_CallObjectWithKeywords () <etc down to 138>
Note the depth of the call stack...
noted.
Is this a problem with psycopg or Zope? Is anyone else seeing it? I'm unable to repro these consistently even under high load, which leads me to think there's an edge case coming into play here - but I don't know what. With -M logging turned on and using requestprofiler, I see:
sincerely i don't know. i am running some SQL Methods right now (with an --enble-devel compiled psycopg) and curs_switch_autocommit() does not get called. what version of zope/psycopg are you using? how have you compiled it? thank you for the report, federico -- Federico Di Gregorio MIXAD LIVE Chief of Research & Technology fog@mixadlive.com Debian GNU/Linux Developer & Italian Press Contact fog@debian.org 99.99999999999999999999% still isn't 100% but sometimes suffice. -- Me