X-Recipient:	archive-cygwin AT delorie DOT com
DKIM-Filter:	OpenDKIM Filter v2.11.0 sourceware.org 223C33887007
DKIM-Signature:	v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com;
	s=default; t=1589683067;
	bh=WlnM9zFBlWE/LDI7QgE41735PxQ9Wg7BMxkn0LKmTi0=;
	h=Date:To:Subject:In-Reply-To:References:List-Id:List-Unsubscribe:
	List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:
	From;
	b=LZ64VooUTd5ydDVxPVwxiz/JSKQs9mug3ZUtGjtAV7f6f0SfgPAh40SnO+ujPgWb9
	MwLqb+zzDF26vcagObjIaPhBoOJSeyC6VCaMBvFruK3y0WXWDejY0taOp7ymbFbMMs
	DDCMrlqwllAoZu0GGAHQlrC2SVTMzVt0J2vzYjU4=
X-Original-To:	cygwin AT cygwin DOT com
Delivered-To:	cygwin AT cygwin DOT com
DMARC-Filter:	OpenDMARC Filter v1.3.2 sourceware.org 482863851C3E
DKIM-Filter:	OpenDKIM Filter v2.10.3 conssluserg-05.nifty.com 04H2bDBU004148
X-Nifty-SrcIP:	[124.155.40.7]
Date:	Sun, 17 May 2020 11:38:05 +0900
To:	cygwin AT cygwin DOT com
Subject:	Re: "ls -la /dev" fails to write output
Message-Id:	<20200517113805.101ec9b25b3e82ccf3ef6a4a@nifty.ne.jp>
In-Reply-To:	<CABPLAST6rT+zgM=6tiwwPGmhyyNNC-S7JqxsFJ_WVsNafmcM-g@mail.gmail.com>
References:	<CABPLASTyj_ZDTyVK9cOy3Drm5EMa-8RaTY503A5fKqSDHTP3Lw AT mail DOT gmail DOT com>
	<20200517040438 DOT d694ad1e7dbd8db975feb741 AT nifty DOT ne DOT jp>
	<CABPLAST6rT+zgM=6tiwwPGmhyyNNC-S7JqxsFJ_WVsNafmcM-g AT mail DOT gmail DOT com>
X-Mailer:	Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32)
Mime-Version:	1.0
X-Spam-Status:	No, score=-4.6 required=5.0 tests=BAYES_00, DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,
	SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2
X-Spam-Checker-Version:	SpamAssassin 3.4.2 (2018-09-13) on
	server2.sourceware.org
X-BeenThere:	cygwin AT cygwin DOT com
X-Mailman-Version:	2.1.29
List-Id:	General Cygwin discussions and problem reports <cygwin.cygwin.com>
List-Unsubscribe:	<http://cygwin.com/mailman/options/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=unsubscribe>
List-Archive:	<https://cygwin.com/pipermail/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-request AT cygwin DOT com?subject=help>
List-Subscribe:	<http://cygwin.com/mailman/listinfo/cygwin>,
	<mailto:cygwin-request AT cygwin DOT com?subject=subscribe>
From:	Takashi Yano via Cygwin <cygwin AT cygwin DOT com>
Reply-To:	Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
Errors-To:	cygwin-bounces AT cygwin DOT com
Sender:	"Cygwin" <cygwin-bounces AT cygwin DOT com>

On Sat, 16 May 2020 21:46:54 +0200
Kacper Michajlow via Cygwin <cygwin AT cygwin DOT com> wrote:
> On Sat, 16 May 2020 at 21:04, Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp> wrote:
> 
> > I cannot reproduce your problem. Could you please provide
> > step by step procedure to reproduce your problem?
> 
> 
> I though I lost it, because indeed there is prerequisite. It fails when
> there is at least one pty allocated.
> 
> STR:
> 1. Open mintty (will allocate pty)
> 2. Open cmd with Cygwin's bash
> 3. ls -la /dev will fail in cmd.

Thanks for the report. The problem does not occur in
cygwin 3.1.4, but occurs in the current git head.

I have just submit a patch for this issue.

-- 
Takashi Yano <takashi DOT yano AT nifty DOT ne DOT jp>
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple

- Raw text -