Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Bug#482346: zsh doesn't always wait for its children (-> zombie)
- X-seq: zsh-workers 25098
- From: Stephane Chazelas <Stephane_Chazelas@xxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Bug#482346: zsh doesn't always wait for its children (-> zombie)
- Date: Sat, 24 May 2008 19:25:46 +0100
- Cc: zsh-workers@xxxxxxxxxx, 482346@xxxxxxxxxxxxxxx
- In-reply-to: <080524104107.ZM15175@xxxxxxxxxxxxxxxxxxxxxx>
- Mail-followup-to: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>, zsh-workers@xxxxxxxxxx, 482346@xxxxxxxxxxxxxxx
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20080521235930.GW7056@xxxxxxxxxxxxxxxxxxx> <20080522233327.GA24953@xxxxxxxx> <080523073940.ZM13804@xxxxxxxxxxxxxxxxxxxxxx> <20080523145722.GA12096@xxxxxxxx> <20080523224305.GN7056@xxxxxxxxxxxxxxxxxxx> <20080524025556.GA30511@xxxxxxxx> <20080524124445.GQ7056@xxxxxxxxxxxxxxxxxxx> <20080524152504.759b27ad@pws-pc> <20080524152704.GA5673@xxxxxxxxxxxxxxx> <080524104107.ZM15175@xxxxxxxxxxxxxxxxxxxxxx>
On Sat, May 24, 2008 at 10:41:07AM -0700, Bart Schaefer wrote:
[...]
> But if *that* were a tight loop, it would mean that signal_suspend()
> isn't working. It'd be nice to know what process or processes send
> the load so high; 100% CPU usage is one thing, but 26+ processes in
> runnable state sounds like another thing entirely.
From the strace and from gdb, it would seem that zsh's
sigsuspend doesn't return, so zsh can't be in any kind of loop
unless I missed something.
Might be some multithreading issue. top -H might help.
--
Stéphane
Messages sorted by:
Reverse Date,
Date,
Thread,
Author