On 2010-11-22 07:39:00 -0800, Bart Schaefer wrote: > On Nov 22, 3:49pm, Vincent Lefevre wrote: > } > } Call graph: > } 993 zexit > } 993 sourcehome > } 993 source > } 993 loop > > This indicates that it's reading your .zlogout file. Anything there > that could account for the behavior? I have the following: ---- source ~/.zdomain ---- which just has "domain=local.prunille". ---- if [[ -n $SSH_AUTH_SOCK ]] then if [[ `whence -w _call_sshagent` == '_call_sshagent: function' ]] then _call_sshagent -r elif [[ -n $SSH_AGENT_PID ]] then eval `ssh-agent -k` fi fi ---- Here "_call_sshagent -r" was executed. I've attached the source of this function. ---- [[ $OSTYPE == linux && $TTY == /dev/tty* ]] && clear [[ $OSTYPE == linux && -n $SSH_CLIENT && ${(M)${(f)"$(/dev/null ---- The OS isn't linux, so nothing should be done here. ---- true ---- So, it seems that zsh froze in _call_sshagent. > This ... > > } 2 exalias > } 1 exalias > } 1 gethashnode > } 1 gethashnode > > ... makes me suspect you've got a recursively-expanding alias involved, > but that's much less certain than that it's .zlogout related. Well, problems started to occur before I tried to exit zsh. There could have been a problem in .zlogout due to an earlier memory corruption or something like that. If this is memory corruption, then this could be the same bug I've been noticing for years... -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / Arénaire project (LIP, ENS-Lyon)