-----BEGIN PGP SIGNED MESSAGE-----
[EMAIL PROTECTED] wrote:
> On Sun, 8 May 2005, Samuel Bieri wrote:
>> I managed to compile GNU debug 6.1.1 on the hp-ux box.
> I hope it wasn't too much trouble. You could have gotten it from here:
>> ---> here I klick on a tal-obect in zope. Zope freezes. Then I kill
>> Program received signal SIGQUIT, Quit.
>> 0x77d2ca58 in __lwp_sema_wait () from /usr/lib/librt.2
>> (gdb) bt
>> # 0 0x77d2ca58 in __lwp_sema_wait () from /usr/lib/librt.2
>> # 1 0x77d2ba78 in sem_wait () from /usr/lib/librt.2
>> # 2 0x77d2ba10 in sem_wait () from /usr/lib/librt.2
>> # 3 0x77d2ba10 in sem_wait () from /usr/lib/librt.2
>> Previous frame identical to this frame (corrupt stack?)
>> Can any experienced zope programmer help me further?
>> What does this mean?
> Looks like a deadlock on a semaphore to me, though I couldn't say where.
> Did you python build pass all of the self tests?
> Did you build your python with the posix threads apis (i.e. not DCE
Good points. In addition, you need to find a way to build Python 2.3.4,
at least (2.3.5 would be; that release fixed a GC bug which was known
to cause segfaults in Zope.
It might be useful to read through the python-dev traffic related to
HP-UX, as well, e.g.:
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Zope maillist - Zope@zope.org
** No cross posts or HTML encoding! **
(Related lists -