From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21333 invoked by alias); 16 Dec 2013 16:25:10 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 32127 Received: (qmail 3904 invoked from network); 16 Dec 2013 16:25:04 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.2 X-Biglobe-Sender: From: "Jun T." Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: padding in vt100 causes 'make check' to hang on FreeBSD Message-Id: <30173FEA-DCF9-480B-A219-232505B4311F@kba.biglobe.ne.jp> Date: Tue, 17 Dec 2013 00:36:54 +0900 To: zsh-workers@zsh.org Mime-Version: 1.0 (Mac OS X Mail 7.0 \(1822\)) X-Mailer: Apple Mail (2.1822) On FreeBSD, 'make check' hangs at X02zlevi.ztst (and other tests which use comptest). The hang is at line 96 of comptest (in comptesteval()): 95: zpty -w zsh ". $tmp" 96: zpty -r -m zsh log_eval "**" || { The actual problem is in the contents of the file $tmp (i.e., "$@" of comptesteval()), in particular line 37: 37: TERM=vt100 Various capabilities of vt100 contain the ancient "padding", and FreeBSD's slave side tputs() actually sends 'null bytes' as paddings before sending the . But the zsh on the master side just considers the 'null byte' as the end of C-string, and the line 96 never returns. If I change the line 37 to 37: TERM=xterm then 'make check' doesn't hang and ends without failure (xterm doesn't contain any padding, of course). Is it OK to replace vt100 with xterm? I guess xterm is 'almost' as portable as vt100, but not 100% sure.