Re: [Zope-dev] RE: [Python 2.3.4c1] nasty LinuxThread problem not solved

Dieter Maurer wrote: > > func=detail&aid=949332&group_id=5470&atid=305470> > > indeed fixes the problem. > > It might introduce other subtle problems but at least none that > are revealed by Python's regression test suite... > > Moreover, I doubt th

RE: [Zope-dev] Segfault and Deadlock

For another way round this issue of segfaults and deadlock when using python 2.2, has anyone tried running Zope with a python built to use the GNU Pth library instead of the system's pthread library? GNU Pth is an entirely user-space library, so I would think it's behavior would remain consist

RE: [Zope-dev] Segfault and Deadlock

I've submitted two patches to the python patch collector is something that should probably work with any pthreads based Unix implementation. It simply unblocks the type of signals that are normally del

RE: [Zope-dev] Segfault and Deadlock

Carl Witty <[EMAIL PROTECTED]> wrote on 05/04/2004 08:18:52 PM: > I don't think it should be tested for in configure (or at compile-time > at all). People will want to have binary distributions that work both > with LinuxThreads and NPTL; some people actually switch back and forth > on an appl

RE: [Zope-dev] Segfault and Deadlock

"Tim Peters" <[EMAIL PROTECTED]> wrote on 05/03/2004 04:41:08 PM: > [EMAIL PROTECTED] > > If someone cares enough to work up a patch, Python's patch tracker is open > all night: > > http://sf.net/tracker/?atid=305470&group_id=5470 I might be willing to try my hand at this, but I could use

RE: [Zope-dev] Segfault and Deadlock

"Tim Peters" <[EMAIL PROTECTED]> wrote on 05/03/2004 03:47:31 PM: > [Dieter Maurer] > I'm not clear on exactly what "blocked" means. It has a very specific meaning with Unix signals. The kernel still has the signal for the process waiting in a queue, but the process has told the kernel that

RE: [Zope-dev] Segfault and Deadlock

Dieter Maurer <[EMAIL PROTECTED]> wrote on 05/03/2004 01:48:57 PM: > The reason why I believe Python is to blame: > > With Python 2.1.3, a SIGSEGV in one thread killed them all; > with Python 2.3.3, a SIGSEGV in one thread kills one > of them (the main thread, not the thread that got t

Re: [Zope-dev] Segfault and Deadlock

Dieter Maurer <[EMAIL PROTECTED]> wrote on 05/02/2004 01:28:48 PM: > Willi Langenberger wrote at 2004-5-2 17:10 +0200: > > What is "NPTL"? It stands for "Native POSIX Thread Library" It is a new threads subsystem that is included in Linux 2.6 that Red Hat has backported into their 2.4 kerne