Date: Fri, 23 Oct 2009 12:42:27 +0200 (CEST) From: Alexander Best <alexbestms@math.uni-muenster.de> To: pluknet <pluknet@gmail.com>, Antony Mawer <lists@mawer.org> Cc: freebsd-hackers@freebsd.org Subject: Re: help needed to fix contrib/ee crash/exit when receiving SIGWINCH Message-ID: <permail-20091023104227f0889e8400002915-a_best01@message-id.uni-muenster.de> In-Reply-To: <a31046fc0910230158w6cf60a20o661252fd9cc64ad7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
pluknet schrieb am 2009-10-23: > 2009/10/23 Antony Mawer <lists@mawer.org>: > > On Fri, Oct 23, 2009 at 1:35 PM, Alexander Best > > <alexbestms@math.uni-muenster.de> wrote: > >> hi everyone, > >> together with hugh mahon (the author of ee) i've been trying to > >> fix a nasty > >> bug in ee. for some reason ee exits (not crashes) and leaves the > >> console > >> corrupted when receiving SIGWINCH (`killall -SIGWINCH ee` should > >> exit all > >> running ee instances). > > I noticed this the other day when working on a new 8.0-RC1 > > system... > > in my case I was using putty (Windows ssh client) to access the > > system > > and maximised the window I had ee running in, and noticed ee just > > dumped me straight to the prompt. > > I am wondering if this has anything to do with the new tty > > subsystem > > in 8.0, as this wasn't a problem I've experienced before under > > 7.x... > No, that's a regression appeared in (FreeBSD'ish? version of) ee > 1.5.0. i'm not so sure this is entirely ee's fault. i just grabbed a really ancient version of ee from http://www.anerd.org/sources/ (ee-1.4.2.src.tgz last modified Jan 2001). yet i see the very same behaviour as with ee 1.5.0. right now it looks more like a tty or ncurses bug. cheers. alex
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?permail-20091023104227f0889e8400002915-a_best01>