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 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]