From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30787 invoked by alias); 9 Jul 2019 18:02:41 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 30092 invoked by uid 89); 9 Jul 2019 18:02:41 -0000 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 Received: from rgout0206.bt.lon5.cpcloud.co.uk (HELO rgout02.bt.lon5.cpcloud.co.uk) (65.20.0.205) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 09 Jul 2019 18:02:39 +0000 X-OWM-Source-IP: 86.162.230.207 (GB) X-OWM-Env-Sender: jonturney@btinternet.com X-VadeSecure-score: verdict=clean score=0/300, class=clean X-SNCR-VADESECURE: CLEAN Received: from [192.168.1.102] (86.162.230.207) by rgout02.bt.lon5.cpcloud.co.uk (9.0.019.26-1) (authenticated as jonturney@btinternet.com) id 5B93D5941C3930E4 for cygwin@cygwin.com; Tue, 9 Jul 2019 19:02:36 +0100 Subject: Re: Question about the ldd output To: The Cygwin Mailing List References: From: Jon Turney Message-ID: Date: Tue, 09 Jul 2019 18:02:00 -0000 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: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2019-07/txt/msg00068.txt.bz2 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