X-Recipient:	archive-cygwin AT delorie DOT com
DomainKey-Signature:	a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:mime-version
	:content-type:content-transfer-encoding; q=dns; s=default; b=FJK
	I4XMLfLmeYB4cK0W8X2elvQ8k/ELYmRgYxctJ7KemJPEUCA5U32oiJuqjbflpbAR
	Z8CJWetoQI15pxxnCcj07VRpzyH+fhk2vu4k87s5iASsLqt3b8Zz6Kj6FBxzFLGT
	owJ7Uc7baEgZtU4eZ/9hZQPfjM+2O3q7JdX2rTto=
DKIM-Signature:	v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:mime-version
	:content-type:content-transfer-encoding; s=default; bh=mIq+l2bP2
	JJr3SMEFr7C8Rs3je4=; b=qGLB8ECX9919UaR5pNcZ7S1P6svanaYGVEifVQzfa
	KjiQt03UIs6HFS2d8TnXIZc2ApOLYkoLqXYzY6zzJAfzMt6fZ7gBTEpS409vu/BG
	ENfFYEtfBJV4a4IqyK3NH7joNb8Et1jMGtGLcmi+J0kRuTBUuwZs3x3/5WH6Tg4+
	7k=
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Authentication-Results:	sourceware.org; auth=none
X-Virus-Found:	No
X-Spam-SWARE-Status:	No, score=-6.4 required=5.0 tests=AWL,BAYES_00,GIT_PATCH_2 autolearn=ham version=3.3.2 spammy=inappropriate
X-HELO:	conssluserg-03.nifty.com
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-03.nifty.com v2HBlnj0028060
X-Nifty-SrcIP:	[175.179.23.201]
Date:	Fri, 17 Mar 2017 20:47:51 +0900
From:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
To:	cygwin AT cygwin DOT com
Subject:	tcsh bug regarding rmstar
Message-Id:	<20170317204751.cb1ef0bf54b0e08101450c7b@nifty.ne.jp>
Mime-Version:	1.0
X-IsSubscribed:	yes

Hello,

Today, I noticed a strange behaviour of tcsh regarding rmstar.
32 bit version of tcsh 6.20.00 stops until interrupted by ^C
when executing 'rm *', if 'rmstar' is set.

This can be reproduced by following steps.

--- form here ---
set rmstar
unalias rm
mkdir testdir
cd testdir
rm *
--- to here ---

I looked into this problem, and found the culprit is that a variable
is defined as inappropriate type. That is, the type of auto variable
'c', defined in function getYN() in sh.func.c, should not be int,
but char.

I cannot reproduce this with 64 bit version, but the issue should
potentially exists in it.

It seems that this is the known issue, and is already fixed in HEAD
of github.
https://github.com/tcsh-org/tcsh

I hope this bug will be fixed in the next release.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -