From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from omta002.cacentral1.a.cloudfilter.net (omta002.cacentral1.a.cloudfilter.net [3.97.99.33]) by sourceware.org (Postfix) with ESMTPS id 70A393858C3A for ; Sat, 20 Nov 2021 00:55:21 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 70A393858C3A Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=systematicsw.ab.ca Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTP id oCXEmJAZBztEjoEf2mhcZN; Sat, 20 Nov 2021 00:55:20 +0000 Received: from [192.168.1.105] ([68.147.0.90]) by cmsmtp with ESMTP id oEf2mX8YKlt4QoEf2m92lz; Sat, 20 Nov 2021 00:55:20 +0000 X-Authority-Analysis: v=2.4 cv=F+dEy4tN c=1 sm=1 tr=0 ts=61984778 a=T+ovY1NZ+FAi/xYICV7Bgg==:117 a=T+ovY1NZ+FAi/xYICV7Bgg==:17 a=IkcTkHD0fZMA:10 a=94nOnFI1EgyDtX4ev68A:9 a=QEXdDO2ut3YA:10 Message-ID: Date: Fri, 19 Nov 2021 17:55:20 -0700 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.3.1 Reply-To: cygwin@cygwin.com Subject: Re: gdb symbolic link bug Content-Language: en-CA To: cygwin@cygwin.com References: <7260a5386b514d2c83db0e6bfa431f5c@v0001wsxm02.flightsafety.com> From: Brian Inglis Organization: Systematic Software In-Reply-To: <7260a5386b514d2c83db0e6bfa431f5c@v0001wsxm02.flightsafety.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4xfApLqthma8+CC2fNjUrj0UgA9YeaxOh9pZbE4V/usrz2OVDXVPdOBClyzI42kxbSEYOiOaUX4qjnO9kXydMjPseBtRZZFkDA9fihJ2qQrQujRhehotWt aMVZB/YS3Xyqz/UnVEfStobo0p6Sct0xnhJazwMZkIBlvZE85XfkZ0bJdfPDs+RQDHCgiImCHps6GzeF2fpHxIU1k9qyKLuX7QM= X-Spam-Status: No, score=-1161.6 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, NICE_REPLY_A, RCVD_IN_BARRACUDACENTRAL, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: cygwin@cygwin.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: , X-List-Received-Date: Sat, 20 Nov 2021 00:55:23 -0000 On 2021-11-19 08:08, Carter, Mark Andrew (Andy) via Cygwin wrote: > Gdb will not run an executable when it is a symbolic link in the post > Cygwin release 3.1.5 form. As seen below I am currently running > Cygwin 3.1.7. I have confirmed this is due to the change of the "ln > -s" implementation. Links created by Cygwin 2.8 and 3.1.0 work with > this gdb version, and links created with Cygwin 3.1.7 do not work > with gdb from Cygwin release 2.8. The following capture demonstrates > the issue. Note the workaround using readlink! > $ uname -a > CYGWIN_NT-10.0 P1163-8573-10 3.1.7(0.340/5/3) 2020-08-22 17:48 x86_64 Cygwin > $ ls -l vital.exe > lrwxrwxrwx 1 p00002737 Domain Users 18 Oct 19 06:59 vital.exe -> ../vital/vital.exe > $ gdb vital.exe > Reading symbols from vital.exe...done. > (gdb) r > Starting program: /home/p00002737/vital/tap/vital.exe > Error creating process /home/p00002737/vital/tap/vital.exe, (error 1920). > (gdb) quit > $ gdb `readlink vital.exe` > Reading symbols from ../vital/vital.exe...done. > (gdb) r > Starting program: /home/p00002737/vital/vital/vital.exe > [New Thread 54032.0xc1e8] > [New Thread 54032.0x10e4] > [New Thread 54032.0xdee8] > [New Thread 54032.0xcd20] > [New Thread 54032.0x8e60] > [New Thread 54032.0xc378] > Thread 6 received signal SIGINT, Interrupt. > [Switching to Thread 54032.0xc378] > 0x00007fff3b4b5a03 in TlsGetValue () from /cygdrive/c/WINDOWS/System32/KERNELBASE.dll > (gdb) Cygwin is a rolling release system where only current releases are supported: Cygwin 3.3.2 and gdb 10.2. Please update Cygwin and gdb to currently supported releases (and if possible rebuild the exe with current compilers and libraries) to see if the bug has been fixed or can still be reproduced. -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in binary units and prefixes, physical quantities in SI.]