X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 457723958C2F DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1606883969; bh=7vr3bQH7vO/+7biAFFr79LkSdaYEFcBpl8tGfEny80M=; 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=XxrIrANZ2JMvzxjI7egUMzFRrsVSol4N/rftA/S+O6psTPA3ffOjKbRTC6mYt8eUw k/N1+D9YWsqrxGm0kHYKZLwT0ivTRi+/nR1niz4pTLAKywjx6wUWKalth9tFGPqWsn tWILWtymd695fisq0h6cjz2Jw8PZm96VRHtqXg5Q= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 4791B3958C1D DKIM-Filter: OpenDKIM Filter v2.10.3 conssluserg-02.nifty.com 0B24csSq031013 X-Nifty-SrcIP: [124.155.38.192] Date: Wed, 2 Dec 2020 13:39:05 +0900 To: cygwin AT cygwin DOT com Subject: Re: cygwin1.dll > 3.1.4: Program execution fails if (WSL-)symlink exists and is present in PATH Message-Id: <20201202133905.6355182479af1f61971dc8a4@nifty.ne.jp> In-Reply-To: <66ac6d01-3ae9-5bd3-46a2-9a4e66647e45@cornell.edu> References: <3160909720eb427892eb38221a611953 AT frims060 DOT wamas DOT com> <66ac6d01-3ae9-5bd3-46a2-9a4e66647e45 AT cornell DOT edu> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 X-Spam-Status: No, score=-1.0 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=no 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 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: Takashi Yano via Cygwin Reply-To: Takashi Yano Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: cygwin-bounces AT cygwin DOT com Sender: "Cygwin" On Tue, 1 Dec 2020 19:13:39 -0500 Ken Brown via Cygwin wrote: > On 12/1/2020 4:24 AM, Mattl Mario wrote: > > Hello, > > > > Since cygwin1.dll version 3.1.5, I observed the following behavior: > > If a symbolic link is existing in the PATH environment, programs (external from Cygwin's system directory) using cygwin1.dll cannot be executed anymore. > > Possibly, because the Cygwin-DLL isn't found anymore. > > > > Steps to reproduce: > > > > cd / > > mkdir link_test > > cp /usr/bin/sed.exe link_test > > ln -s link_test test > > export PATH=/test:/link_test:/usr/bin:/bin > > > > /link_test/sed cannot be executed > > $ ldd /link_test/sed > > ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffffd960000) > > KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffffd140000) > > KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffffa8e0000) > > SYSFER.DLL => /cygdrive/c/WINDOWS/System32/SYSFER.DLL (0x550c0000) > > > > -> no cygwin- DLLs found > > > > If I delete the symbolic link > > $ ll test > > lrwxrwxrwx 1 mmattl Users 9 Dec 1 10:14 test -> link_test/ > > simply with > > rm test > > > > everything is working fine; sed can be executed > > $ /link_test/sed > > Usage: /link_test/sed [OPTION]... {script-only-if-no-other-script} [input-file]... > > [...] > > And > > > > $ ldd /link_test/sed > > ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffffd960000) > > KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffffd140000) > > KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffffa8e0000) > > SYSFER.DLL => /cygdrive/c/WINDOWS/System32/SYSFER.DLL (0x550c0000) > > cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000) > > cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3f7110000) > > cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3f7160000) > > > > It would be great if you could give some advice to this issue. > > I think this was fixed by commit 4b4fffe0f2390be6a5be27b6a3ceaa212a3724b2, but I > don't have time to check carefully, and I'm going to be AFK for a few days > starting tomorrow. I can reproduce this issue with current git head even with the commit 4b4fffe0f2390be6a5be27b6a3ceaa212a3724b2. -- Takashi Yano -- 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