Date: Sat, 30 Jun 2007 16:53:58 +0100 From: Rui Paulo <rpaulo@fnop.net> To: Steve Kargl <sgk@troutmask.apl.washington.edu> Cc: Michiel Boland <michiel@boland.org>, freebsd-current@freebsd.org Subject: Re: tcsh hangs in sigsuspend Message-ID: <86wsxlv3op.wl%rpaulo@fnop.net> In-Reply-To: <20070630154013.GA71065@troutmask.apl.washington.edu> References: <Pine.GSO.4.64.0706301632320.29496@neerbosch.nijmegen.internl.net> <20070630150448.GA70741@troutmask.apl.washington.edu> <86zm2hv506.wl%rpaulo@fnop.net> <20070630154013.GA71065@troutmask.apl.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At Sat, 30 Jun 2007 08:40:13 -0700, Steve Kargl wrote: > > 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. Yes. I know. > 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?" IMHO, a fix would be much better than backing out 6.15.00. -- Rui Paulo
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86wsxlv3op.wl%rpaulo>