Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jul 2012 22:30:15 GMT
From:      Peter Jeremy <peter@rulingia.com>
To:        freebsd-bugs@FreeBSD.org
Subject:   Re: kern/169603: Possible r237738 libedit regression resizing windows in terminal programs
Message-ID:  <201207042230.q64MUFN8024305@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/169603; it has been noted by GNATS.

From: Peter Jeremy <peter@rulingia.com>
To: FreeBSD-gnats-submit@FreeBSD.org, freebsd-bugs@FreeBSD.org,
        David Shao <davshao@gmail.com>
Cc:  
Subject: Re: kern/169603: Possible r237738 libedit regression resizing
 windows in terminal programs
Date: Thu, 5 Jul 2012 08:21:01 +1000

 --aVD9QWMuhilNxW9f
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 I am seeing a similar problem with 9-stable/amd64 (r237995) - sh(1)
 now exits if I change the window size (ssh'ing to the target system
 within an xterm).
 
 ktrace output looks like:
   1766 sh       GIO   fd 2 wrote 2 bytes
        "# "
   1766 sh       RET   write 2
   1766 sh       CALL  ioctl(0,TIOCGETA,0x801020364)
   1766 sh       RET   ioctl 0
   1766 sh       CALL  ioctl(0,TIOCSETAW,0x801020338)
   1766 sh       RET   ioctl 0
   1766 sh       CALL  read(0,0x7fffffffda8f,0x1)
   1766 sh       RET   read -1 errno 4 Interrupted system call
   1766 sh       PSIG  SIGWINCH caught handler=3D0x417d10 mask=3D0x0 code=3D=
 0x10006
   1766 sh       CALL  sigreturn(0x7fffffffd600)
   1766 sh       RET   sigreturn JUSTRETURN
   1766 sh       CALL  ioctl(0,TIOCSETAW,0x80102030c)
   1766 sh       RET   ioctl 0
   1766 sh       CALL  setpgid(0,0x6e6)
   1766 sh       RET   setpgid -1 errno 1 Operation not permitted
   1766 sh       CALL  ioctl(0xa,TIOCSPGRP,0x7fffffffda74)
   1766 sh       RET   ioctl 0
   1766 sh       CALL  close(0xa)
   1766 sh       RET   close 0
   1766 sh       CALL  exit(0)
 
 Reverting r237738 (the MFC of r237448), as suggested by pfg@, fixes the
 problem.  Unfortunately this is quite a large commit and I haven't
 looked into the specific change that breaks SIGWINCH handling.
 
 --=20
 Peter Jeremy
 
 --aVD9QWMuhilNxW9f
 Content-Type: application/pgp-signature
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v2.0.19 (FreeBSD)
 
 iEYEARECAAYFAk/0wc0ACgkQ/opHv/APuIfuPQCgkyndvzwlYXBsVF3N55+r1V/P
 6pUAn326qQ1i9kI9HkbTHX1Z6mEL/XWv
 =62+O
 -----END PGP SIGNATURE-----
 
 --aVD9QWMuhilNxW9f--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201207042230.q64MUFN8024305>