Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-26 Thread Donovan Baarda
On Wed, 2005-01-26 at 01:53 +1100, Anthony Baxter wrote: > On Wednesday 26 January 2005 01:01, Donovan Baarda wrote: > > In this case it turns out to be "don't do exec() in a thread, because what > > you exec can have all it's signals masked". That turns out to be a hell of > > a lot of things; pop

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-25 Thread Anthony Baxter
On Wednesday 26 January 2005 01:01, Donovan Baarda wrote: > In this case it turns out to be "don't do exec() in a thread, because what > you exec can have all it's signals masked". That turns out to be a hell of > a lot of things; popen, os.command, etc. They all only work OK in a > threaded applic

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-25 Thread Donovan Baarda
G'day, From: "Anthony Baxter" <[EMAIL PROTECTED]> > On Thursday 20 January 2005 12:43, Donovan Baarda wrote: > > On Wed, 2005-01-19 at 13:37 +, Michael Hudson wrote: > > > The main oddness about python threads (before 2.3) is that they run > > > with all signals masked. You could play with a

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-24 Thread Anthony Baxter
On Thursday 20 January 2005 12:43, Donovan Baarda wrote: > On Wed, 2005-01-19 at 13:37 +, Michael Hudson wrote: > > The main oddness about python threads (before 2.3) is that they run > > with all signals masked. You could play with a C wrapper (call > > setprocmask, then exec fop) to see if t

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-21 Thread Michael Hudson
Donovan Baarda <[EMAIL PROTECTED]> writes: > On Thu, 2005-01-20 at 14:12 +, Michael Hudson wrote: >> Donovan Baarda <[EMAIL PROTECTED]> writes: >> >> > On Wed, 2005-01-19 at 13:37 +, Michael Hudson wrote: >> >> Donovan Baarda <[EMAIL PROTECTED]> writes: > [...] >> >> The main oddness abou

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-20 Thread Donovan Baarda
On Thu, 2005-01-20 at 14:12 +, Michael Hudson wrote: > Donovan Baarda <[EMAIL PROTECTED]> writes: > > > On Wed, 2005-01-19 at 13:37 +, Michael Hudson wrote: > >> Donovan Baarda <[EMAIL PROTECTED]> writes: [...] > >> The main oddness about python threads (before 2.3) is that they run > >> w

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-20 Thread Michael Hudson
Donovan Baarda <[EMAIL PROTECTED]> writes: > On Wed, 2005-01-19 at 13:37 +, Michael Hudson wrote: >> Donovan Baarda <[EMAIL PROTECTED]> writes: > [...] >> You've left out a very important piece of information: which version >> of Python you are using. I'm guessing 2.3.4. Can you try 2.4? > >

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-19 Thread Donovan Baarda
On Wed, 2005-01-19 at 13:37 +, Michael Hudson wrote: > Donovan Baarda <[EMAIL PROTECTED]> writes: [...] > You've left out a very important piece of information: which version > of Python you are using. I'm guessing 2.3.4. Can you try 2.4? Debian Python2.3 (2.3.4-18), Debian kernel-image-2.6.

Re: [Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-19 Thread Michael Hudson
Donovan Baarda <[EMAIL PROTECTED]> writes: > G'day, > > I've Cc'ed this to zope-coders as it might affect other Zope developers > and it had me stumped for ages. I couldn't find anything on it anywhere, > so I figured it would be good to get something into google :-). > > We are developing a Zope2

[Python-Dev] Strange segfault in Python threads and linux kernel 2.6

2005-01-18 Thread Donovan Baarda
G'day, I've Cc'ed this to zope-coders as it might affect other Zope developers and it had me stumped for ages. I couldn't find anything on it anywhere, so I figured it would be good to get something into google :-). We are developing a Zope2.7 application on Debian GNU/Linux that is using fop to