Date: Thu, 22 Oct 2009 21:10:04 -0700 (PDT) From: Nate Eldredge <nate@thatsmathematics.com> To: Antony Mawer <lists@mawer.org> Cc: freebsd-hackers@freebsd.org, Alexander Best <alexbestms@math.uni-muenster.de> Subject: Re: help needed to fix contrib/ee crash/exit when receiving SIGWINCH Message-ID: <Pine.GSO.4.64.0910222108490.5432@zeno.ucsd.edu> In-Reply-To: <ea2d4a5b0910222102w1269d071o221a42e9ee85f5b7@mail.gmail.com> References: <permail-20091023023507f0889e8400001398-a_best01@message-id.uni-muenster.de> <ea2d4a5b0910222102w1269d071o221a42e9ee85f5b7@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 23 Oct 2009, Antony Mawer wrote: > 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. Seems a good start might be to compile ncurses with -g, link ee against it, put a breakpoint on the SIGWINCH handler, and start single stepping... -- Nate Eldredge nate@thatsmathematics.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.64.0910222108490.5432>