From owner-freebsd-bugs@FreeBSD.ORG  Sun Feb 27 07:31:41 2011
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id B8C2E106566C;
	Sun, 27 Feb 2011 07:31:41 +0000 (UTC) (envelope-from stb@lassitu.de)
Received: from gilb.zs64.net (gilb.zs64.net [IPv6:2001:470:1f0b:105e::1ea])
	by mx1.freebsd.org (Postfix) with ESMTP id 7D9EF8FC12;
	Sun, 27 Feb 2011 07:31:41 +0000 (UTC)
Received: by gilb.zs64.net (Postfix, from stb@lassitu.de) id E1A59E266;
	Sun, 27 Feb 2011 08:31:39 +0100 (CET)
Mime-Version: 1.0 (Apple Message framework v1082)
Content-Type: text/plain; charset=us-ascii
From: Stefan Bethke <stb@lassitu.de>
In-Reply-To: <201102241311.p1ODBajF050380@freefall.freebsd.org>
Date: Sun, 27 Feb 2011 08:31:43 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <83C33215-1358-4606-A7A8-FC40BCC08E69@lassitu.de>
References: <201102241311.p1ODBajF050380@freefall.freebsd.org>
To: eadler@FreeBSD.org
X-Mailer: Apple Mail (2.1082)
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: gnu/137665: [patch] dialog(1) goes into tight loop on
	encountering eof
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 27 Feb 2011 07:31:41 -0000

On:
# uname -a
FreeBSD freebsd-current.lassitu.de 9.0-CURRENT FreeBSD 9.0-CURRENT #0 =
r219066: Sun Feb 27 01:55:21 CET 2011     =
root@freebsd-current.lassitu.de:/usr/obj/usr/src/sys/MINIMAL  amd64

dialog does not go into a tight loop eating all CPU, but it still gets =
stuck.  I believe it should take some action on encountering EOF, =
instead of waiting for input forever.  My patch did that for the old =
dialog, typically taking the same path as pressing ESC would.


Stefan

--=20
Stefan Bethke <stb@lassitu.de>   Fon +49 151 14070811