From: "Bart Schaefer" <schaefer@brasslantern.com>
To: Tatsuo Furukawa <frkwtto@osk3.3web.ne.jp>, zsh-workers@sunsite.auc.dk
Subject: Re: zsh hangs (3.0.6-pre-2, 3.1.5-pws-16)
Date: Thu, 29 Apr 1999 09:01:22 -0700 [thread overview]
Message-ID: <990429090122.ZM8426@candle.brasslantern.com> (raw)
In-Reply-To: <199904290549.OAA26192@pop1.ngy.3web.ne.jp>
On Apr 29, 2:28pm, Tatsuo Furukawa wrote:
} Subject: zsh hangs (3.0.6-pre-2, 3.1.5-pws-16)
}
} 1. Write following in .zshrc
}
} RPROMPT="(%l)"
}
} function TRAPWINCH() {
} eval $(resize)
} echo;
} echo "resized";
} echo
} }
}
} 4. Change terminal size using mouse.
}
} Then "resized" message is displayed, and RPROMPT is displayed into
} 'right' place. (But why is "resized" message displayed twice?)
The message is displayed twice because the "resize" command itself causes
a SIGWINCH to be sent. So you get one when xterm finishes remapping, and
another when resize runs. I'm not entirely sure why this doesn't cause
an infinite loop; perhaps resize only sends a SIGWINCH when the values it
reads back from the terminal do not match what's in the environment.
The hang appears to be a race condition in exec.c: getoutput(). Zsh is
blocked forever in sigsuspend() waiting for the SIGCHLD that will tell
it `resize` has exited. Probably that signal arrived while zsh was
handling the SIGWINCH sent by "resize" and zsh either improperly handled
it then or dropped it on the floor.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
next prev parent reply other threads:[~1999-04-29 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-29 5:28 Tatsuo Furukawa
1999-04-29 16:01 ` Bart Schaefer [this message]
1999-05-04 16:48 ` PATCH: " Bart Schaefer
1999-05-04 17:12 ` Bart Schaefer
1999-05-11 14:41 ` Tatsuo Furukawa
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=990429090122.ZM8426@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=frkwtto@osk3.3web.ne.jp \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).