X-Recipient: archive-cygwin@delorie.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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; q=dns; s=default; b=si1a/Saa1czpR7qv D6uNlRq+7cbL7Vnu9G+hryzzRP8Yv1jh/Z4j7I+SXnCXR1U87X7V5KQxY8RYKvM/ AYL4N7ik4T3/99MEaCS38NTu+A09Qy1wu+iiotWP1GK0nRYTiwxKGWBXbp1IyXNu cd/uvY5PdJ9bwarvGMYzs6iFej8= 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:reply-to:subject:to:references:from:message-id :date:mime-version:in-reply-to:content-type :content-transfer-encoding; s=default; bh=ZoRXTbGWw4rSxVIvGESEuz vk6JE=; b=Gb5s8TaWcmKghRHlsNjjA5lZRnVN9ImjomRlyGQqKgGDFCdiTzIIIM j2E3PO/mw7+E8VpEJYldRv7Epd/NNveaVNioW6turKJccDoAn1GXpM0+jja543CJ MezzKxsm2FjLFnd/iWtgtqjzUiLN6IdSqaAv76WedYHqn5XGkmrL8= Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-2.6 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=Lavrentiev, NLM, ncbi, NCBI X-HELO: smtp-out-so.shaw.ca Reply-To: Brian.Inglis@SystematicSw.ab.ca Subject: Re: Question about the ldd output To: cygwin@cygwin.com References: From: Brian Inglis Openpgp: preference=signencrypt Message-ID: Date: Tue, 9 Jul 2019 10:40:42 -0600 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 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes 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)? > > 1. > ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffc339d0000) > KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffc31a00000) > KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffc30090000) > cygbz2-1.dll => /usr/bin/cygbz2-1.dll (0x3f6a40000) > cygcom_err-2.dll => /usr/bin/cygcom_err-2.dll (0x3ef750000) > cyggssapi_krb5-2.dll => /usr/bin/cyggssapi_krb5-2.dll (0x3eceb0000) > cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3ec980000) > cygpcre-1.dll => /usr/bin/cygpcre-1.dll (0x3eb1a0000) > cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3ee3a0000) > cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3ea280000) > cygz.dll => /cygdrive/u/2.4.0/release/Cygwin-64/bin/cygz.dll (0x3aba30000) > cygk5crypto-3.dll => /usr/bin/cygk5crypto-3.dll (0x3ec300000) > cygwin1.dll => /cygdrive/u/2.4.0/release/Cygwin-64/bin/cygwin1.dll (0x180040000) > ??? => ??? (0xe80000) > ??? => ??? (0x1440000) > ??? => ??? (0xe80000) > cygkrb5-3.dll => /usr/bin/cygkrb5-3.dll (0x3ec170000) > cygkrb5support-0.dll => /usr/bin/cygkrb5support-0.dll (0x3ec150000) > cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3ec8d0000) > > 2. > ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffc339d0000) > KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL (0x7ffc31a00000) > KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll (0x7ffc30090000) > cygbz2-1.dll => /usr/bin/cygbz2-1.dll (0x3f6a40000) > cygcom_err-2.dll => /usr/bin/cygcom_err-2.dll (0x3ef750000) > cyggssapi_krb5-2.dll => /usr/bin/cyggssapi_krb5-2.dll (0x3eceb0000) > cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3ec980000) > cygpcre-1.dll => /usr/bin/cygpcre-1.dll (0x3eb1a0000) > cygwin1.dll => /cygdrive/u/2.4.0/release/Cygwin-64/bin/cygwin1.dll (0x180040000) > cyggcc_s-seh-1.dll => /usr/bin/cyggcc_s-seh-1.dll (0x3ee3a0000) > cygstdc++-6.dll => /usr/bin/cygstdc++-6.dll (0x3ea280000) > cygk5crypto-3.dll => /usr/bin/cygk5crypto-3.dll (0x3ec300000) > cygkrb5-3.dll => /usr/bin/cygkrb5-3.dll (0x3ec170000) > cygz.dll => /cygdrive/u/2.4.0/release/Cygwin-64/bin/cygz.dll (0x3aba30000) > cygkrb5support-0.dll => /usr/bin/cygkrb5support-0.dll (0x3ec150000) > cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3ec8d0000) 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. -- 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. -- 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