Date: Sat, 24 Oct 1998 07:43:18 -0400 (EDT) From: robert@fledge.watson.org To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/8438: ex/vi: Error: tcsetattr: Interrupted system call Message-ID: <199810241143.HAA15863@sleipnir.watson.org>
next in thread | raw e-mail | index | archive | help
>Number: 8438 >Category: bin >Synopsis: ex/vi: Error: tcsetattr: Interrupted system call >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sat Oct 24 20:00:00 PDT 1998 >Last-Modified: >Originator: Robert Watson >Organization: >Release: FreeBSD 3.0-BETA i386 >Environment: 3.0-BETA/RELEASE, using vi against a file in the local FFS file system /usr. X-windows using xterm, XiG's X server for notebooks. >Description: When resizing an xterm and using vi, once in a while I get: ex/vi: Error: tcsetattr: Interrupted system call This kills vi. This is not good. I believe I have observed this both in command and edit modes. >How-To-Repeat: Start editing a file. Now resize your xterm. This does not always appear to happen -- in fact, only infrequently. I'm not sure if there is a correspondence to the size of the file being edited. I am unable to repeat this consistently, but it has happened at least a few times in the past few months. >Fix: I'm on the road, so can't check the source or see if there is already a PR in for this. However, I'd guess that something in curses/ncurses/ whatever vi uses doesn't wrap a syscall in a check for EINTR, and this results in vi terminating from an error it does not expect. >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810241143.HAA15863>