[Python-Dev] Strange segfault in Python threads and linux kernel 2.6 (original) (raw)

Anthony Baxter anthony at interlink.com.au
Tue Jan 25 15:53:20 CET 2005

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 application if what you are exec'ing doesn't use any signals.

Yep. You just have to be aware of it. We do a bit of this at work, and we either spool via a database table, or a directory full of spool files.

Actually, I've noticed that zope often has a sorta zombie "which" process which it spawns. I wonder it this is a stuck thread waiting for some signal...

Quite likely.

-- Anthony Baxter <anthony at interlink.com.au> It's never too late to have a happy childhood.

More information about the Python-Dev mailing list