Hi Zope (and Python) experts!
There seems to be a problem when an external python module segfaults
during a zope request. The remaining worker threads are deadlocked.
I think this is the same problem as Dieter pointed out in his message
to zope-dev [Problem] strange state after SIGSEGV:
Willi Langenberger wrote at 2004-5-2 17:10 +0200:
...
The reason is the way python handles threads on some systems
(RedHat-7.3, kernel 2.4.20, without NPTL).
What is NPTL?
...
PS: A RedHat-9 system (kernel 2.4.20, with NPTL) shows a different
behaviour. After the segfault, all threads
According to Dieter Maurer:
The reason is the way python handles threads on some systems
(RedHat-7.3, kernel 2.4.20, without NPTL).
What is NPTL?
Native POSIX Thread Library.
That is the good behaviour. Thus, we only have to learn
how we can get NPTL for all Linux systems.
However, i
Am 2. Mai 2004 um 13:28 schrieb Dieter Maurer:
Willi Langenberger wrote at 2004-5-2 17:10 +0200:
...
The reason is the way python handles threads on some systems
(RedHat-7.3, kernel 2.4.20, without NPTL).
What is NPTL?
The native posix thread library or something like that. It's a new
threading
[EMAIL PROTECTED]
Hi Zope (and Python) experts!
There seems to be a problem when an external python module segfaults
during a zope request. The remaining worker threads are deadlocked.
Maybe, maybe not. Python (and so also Zope) use platform-native thread
facilities, and what happens when
