> From: Dieter Maurer [mailto:[EMAIL PROTECTED]
>
> I fear that you can call Python functions in general only on
> the current thread (the other's probably lack the GIL,
> an essential requirement to execute Python code).
Well, I upgraded to Python 2.4, re-compiled Zope and friends, and
updated a
Matthew X. Economou wrote at 2006-6-18 11:53 -0400:
>I tried the whole gdb threads debugging thing, with the following (nil)
>results. Any other ideas? A lot of the instructions online seem to be
>Linux-centric, so I'm at a loss as how to proceed:
>
>(gdb) info threads
> ...
> 2 Thread 0x9064e00
This time, when it locked, I thought to try a backtrace.
(gdb) info threads
* 7 LWP 100098 0x2820e544 in pthread_mutexattr_init () from
/usr/lib/libpthread.so.2
6 Thread 0x8111000 (sleeping) 0x2820df0f in pthread_mutexattr_init ()
from /usr/lib/libpthread.so.2
5 Thread 0xa1e1a00 (LWP 100047)
; From: Dieter Maurer [mailto:[EMAIL PROTECTED]
> Sent: Friday, June 16, 2006 2:36 PM
> To: Matthew X. Economou
> Cc: zope@zope.org
> Subject: Re: [Zope] DeadlockDebugger revisited
>
> Matthew X. Economou wrote at 2006-6-16 09:10 -0400:
> >I thought a recent operating system u
Matthew X. Economou wrote at 2006-6-16 09:10 -0400:
>I thought a recent operating system upgrade (FreeBSD 5.4 to 6.1) fixed
>my problems with Zope. Unfortunately, once I re-compiled Python et al
>(to remove dependencies on the old libraries), my problems with Zope
>deadlocking recurred. I tried t
