On 09/20/2010 12:44 PM, Illia Bobyr wrote:
It may be a Cygwin specific problem. Approximately at the time the
problem appeared cygwin.dll was also updated.
This is a known cygwin problem, caused by the fact that cygwin tcl is
not cygwin-aware, which makes cygwin have a tough time knowinghow to
manage controlling ttys across a parent and grandchild process with a
non-cygwin process in the middle:
http://cygwin.com/ml/cygwin/2010-09/msg00641.html
Bash may yet have a bug where it over-reacts to a failed tty ioctl, by
exiting instead of reporting the problem, but if that turns out to be
the case, I will follow up here with more details.
--
Eric Blake ebl...@redhat.com +1-801-349-2682
Libvirt virtualization library http://libvirt.org
