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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=uPeuv+BD5cMTHvU5
	0EgX3Dhx7mFHcm8WhSMCdG6yiecN/hzxAOCw1m+aehUtv+idmStKqqmLZ3WBLZW6
	/zQ6n7pjex2ey+Nadqgk1Rz2QSMklNGNlnYoqmxoP0ePLri0lOLG1/374ASUQW0f
	yrIZQ7dVjtK5zG+NxpkM97XOlYw=
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:subject:to:references:from:message-id:date
	:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=OG8Oa0mo/LOYCBcgt6Ns0i
	rL5lQ=; b=kTqkbB5TZo3935DhRV4WbUHxha6T93Ni0uJFIfyS1fkIDwRy4Ethho
	vrorukatYC0OlM9Q0EQaayO8gqwQKLjYI4a2XjmMoJzVwc2UKMj3cqfb72KDpIJi
	ZVjTC2gmEVnDCyGzcvathf1KQP0BoinubnLPUoyD4/zmbW3f7E0YY=
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-Spam-SWARE-Status: No, score=-4.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=
X-HELO: rgout02.bt.lon5.cpcloud.co.uk
X-OWM-Source-IP: 86.162.230.207 (GB)
X-OWM-Env-Sender: jonturney AT btinternet DOT com
X-VadeSecure-score: verdict=clean score=0/300, class=clean
X-SNCR-VADESECURE: CLEAN
Subject: Re: Question about the ldd output
To: The Cygwin Mailing List <cygwin AT cygwin DOT com>
References: <BN6PR09MB2227BA2644949DB75A67A6B2A5F60 AT BN6PR09MB2227 DOT namprd09 DOT prod DOT outlook DOT com> <ee7608a2-2e13-d2eb-6410-c07362d75296 AT SystematicSw DOT ab DOT ca>
From: Jon Turney <jon DOT turney AT dronecode DOT org DOT uk>
Message-ID: <e0e8c9db-bd7a-638c-0bb5-88c43c5f9d98@dronecode.org.uk>
Date: Tue, 9 Jul 2019 19:02:35 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.7.2
MIME-Version: 1.0
In-Reply-To: <ee7608a2-2e13-d2eb-6410-c07362d75296@SystematicSw.ab.ca>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit

On 09/07/2019 17:40, Brian Inglis wrote:
> On 2019-07-08 12:00, Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin wrote:
>> Well, I don't think there's anything special that Cygwin does to load executables, because these are essentially Windows processes, so they are loaded by Windows, first and foremost.
>>
>> But it gets even weirder.  Below are two _consecutive!_ runs of ldd on the very same executable.  Why the output differs so drastically (including the unknown dlls all of a sudden)?

This is probably a 'bug'.

> Libraries may be loaded asynchronously as they are accessed, and ldd just dumps
> the dll import table once the subprocess is ready to run.
> Perhaps these are import entries that ldd should detect and skip or annotate in
> some more useful way.

Please don't spread misinformation based upon guessing how Cygwin's ldd 
works.

It's not necessary, as the source code is available [1] :)

[1] 
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git;a=history;f=winsup/utils/ldd.cc


--
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