Re: sh(1) exiting on SIGWINCH

2012-07-05 Thread Pedro Giffuni
Hello; --- Gio 5/7/12, Peter Jeremy ha scritto: ... > > pfg@ (who shepherded the libedit update into the tree), David Shao > (originator of kern/169603) and I have been investigating fixes to > libedit but do not have a solution yet. The following partial revert fixes things for me: http://peo

Re: sh(1) exiting on SIGWINCH

2012-07-05 Thread Pedro Giffuni
Hello guys; --- Gio 5/7/12, Peter Jeremy ha scritto: > Brandon Gooch wrote: > >Seems that the window resize is somehow causing sh(1) to receive an > >EOF while the shell is sitting at the prompt, which results in the > >shell exiting; haven't dug too deeply into the source yet, but can you > >t

Re: sh(1) exiting on SIGWINCH

2012-07-05 Thread Peter Jeremy
On 2012-Jul-05 00:22:45 -0500, Brandon Gooch wrote: >Seems that the window resize is somehow causing sh(1) to receive an >EOF while the shell is sitting at the prompt, which results in the >shell exiting; haven't dug too deeply into the source yet, but can you >try to run /bin/sh with the '-I' (t

Re: sh(1) exiting on SIGWINCH

2012-07-04 Thread Brandon Gooch
On Wed, Jul 4, 2012 at 5:08 PM, Peter Jeremy wrote: > On 2012-Jul-04 20:03:32 +1000, Peter Jeremy wrote: >>I've recently updated a box from 8-stable to 9-stable/amd64 (r237995), >>compiled with gcc, and now sh(1) exits if I change the window size >>(ssh'ing to the target system within an xterm).

Re: sh(1) exiting on SIGWINCH

2012-07-04 Thread Peter Jeremy
On 2012-Jul-04 20:03:32 +1000, Peter Jeremy wrote: >I've recently updated a box from 8-stable to 9-stable/amd64 (r237995), >compiled with gcc, and now sh(1) exits if I change the window size >(ssh'ing to the target system within an xterm). I don't recall ever >seeing this sort of behaviour before

sh(1) exiting on SIGWINCH

2012-07-04 Thread Peter Jeremy
I've recently updated a box from 8-stable to 9-stable/amd64 (r237995), compiled with gcc, and now sh(1) exits if I change the window size (ssh'ing to the target system within an xterm). I don't recall ever seeing this sort of behaviour before and am still trying to track down the relevant code pat