help needed to fix contrib/ee crash/exit when receiving SIGWINCH
gary.jennejohn at freenet.de
Fri Oct 23 12:00:52 UTC 2009
On Fri, 23 Oct 2009 13:50:24 +0200
Gary Jennejohn <gary.jennejohn at freenet.de> wrote:
> On Fri, 23 Oct 2009 12:58:43 +0400
> pluknet <pluknet at gmail.com> wrote:
> > 2009/10/23 Antony Mawer <lists at mawer.org>:
> > > On Fri, Oct 23, 2009 at 1:35 PM, Alexander Best
> > > <alexbestms at 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.
> SIGWINCH is handled in new_curse.c, but it's not being compiled/linked.
Never mind - I see that new_curse.c is supposed to be a substitute for
ncurses if it's not available on the system.
Sorry for the noise.
More information about the freebsd-hackers