Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

zsh bugs

Dear Sir/Madam,

I was wondering if you can help me with a zsh (version 2.5.03) bug.  When we 
are running a zsh and then run another zsh on top of it.  Then if we exit
(by killing our X session) it automatically sends a SIGHUP to the first 
(parent) zsh and the second (child) zsh.  This will automatically kill the
second zsh, but not the first (we put a TRAPHUP to exit when the zsh got this 
signal).  The first zsh then become a wild process and consumes a fair bit of 
processing power.

Debugging it gave me some clue where it got stuck.  It got stuck in zle_main.c
source in line 254:

           while ( r=read(...... )
              if ( r == 0 ) {
                 if ( isset (IGNOREEOF ) )

My guess is that this process is trying to read a pipe from somewhere and keep
getting no message and then when it encounter the "continue" statement it
just loops back again and again,  which is what the debugger shows.

Is there already a patch to fix this problem or perhaps you can suggest a 
solution to us.  

Many thanks,

Roy Limley

Messages sorted by: Reverse Date, Date, Thread, Author