From owner-freebsd-current@FreeBSD.ORG Sat Jun 30 15:41:14 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 77DA716A468 for ; Sat, 30 Jun 2007 15:41:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.freebsd.org (Postfix) with ESMTP id 5AD8113C45E for ; Sat, 30 Jun 2007 15:41:14 +0000 (UTC) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost.apl.washington.edu [127.0.0.1]) by troutmask.apl.washington.edu (8.14.1/8.13.8) with ESMTP id l5UFeHe6071116; Sat, 30 Jun 2007 08:40:17 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.14.1/8.13.8/Submit) id l5UFeDJl071115; Sat, 30 Jun 2007 08:40:13 -0700 (PDT) (envelope-from sgk) Date: Sat, 30 Jun 2007 08:40:13 -0700 From: Steve Kargl To: Rui Paulo Message-ID: <20070630154013.GA71065@troutmask.apl.washington.edu> References: <20070630150448.GA70741@troutmask.apl.washington.edu> <86zm2hv506.wl%rpaulo@fnop.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <86zm2hv506.wl%rpaulo@fnop.net> User-Agent: Mutt/1.4.2.2i Cc: Michiel Boland , freebsd-current@freebsd.org Subject: Re: tcsh hangs in sigsuspend X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2007 15:41:14 -0000 On Sat, Jun 30, 2007 at 04:25:29PM +0100, Rui Paulo wrote: > At Sat, 30 Jun 2007 08:04:48 -0700, > Steve Kargl wrote: > > I suspect it is the same problem. Unfortunately, the author of > > tcsh does not have a publicly available source tree, so one cannot > > determine if the problem is fixed. It looks like you've managed > > to go beyond the limited debugging I did in bin/112408. Hopefully, > > this gets addressed before 7.0 is released. > > But you can consult the bug tracking system at http://bugs.gw.com/ > ROTFL. http://bugs.gw.com/view.php?id=52 This URL points to http://mx.gw.com/pipermail/tcsh-bugs/2007-May/000498.html which is due to bin/112408. I've repeatedly asked to have the import of tcsh 6.15.00 backed out to the old 6.14.00 version. Having 7.0 released with a broken default user shell seems to be a lack of QA. A more important question is "can the broken signal handling in tcsh be exploited?" -- Steve