From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Why does ldd not show cyg*.dll in its output?
Date: Mon, 16 May 2016 17:50:00 -0000 [thread overview]
Message-ID: <4b37d689-285d-7dd4-3e3d-d40b4ee2f81f@cygwin.com> (raw)
In-Reply-To: <3AD694B4-17D4-4963-88FD-435AD4DD36D5@etr-usa.com>
On 2016-05-16 10:42, Warren Young wrote:
> $ ldd `which ls`
> ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffd16fb0000)
> KERNEL32.DLL => /c/WINDOWS/system32/KERNEL32.DLL (0x7ffd16b80000)
> KERNELBASE.dll => /c/WINDOWS/system32/KERNELBASE.dll (0x7ffd13f50000)
WFM:
$ /bin/ldd /bin/ls
ntdll.dll => /cygdrive/c/Windows/SYSTEM32/ntdll.dll (0x77c90000)
kernel32.dll => /cygdrive/c/Windows/system32/kernel32.dll
(0x77a70000)
KERNELBASE.dll => /cygdrive/c/Windows/system32/KERNELBASE.dll
(0x7fefdb10000)
cygwin1.dll => /usr/bin/cygwin1.dll (0x180040000)
cygintl-8.dll => /usr/bin/cygintl-8.dll (0x3d4e00000)
cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x3d8b50000)
> Expected output:
>
> According to Microsoftâs Dependency Walker tool, the output should also list
> cygwin1.dll and cygintl-8.dll, at minimum. Since it seems happy to chase
> dependencies from kernel32.dll to the other two, which are not explicit
> dependencies of ls.exe, it should also list cygiconv-2.dll, via cygintl.
See above.
> Bonus points if the output changes to a tree view, so the indirect dependencies are clear.
ldd is meant to be compatible with the Linux tool. As Andrey mentioned,
use cygcheck instead if you want that layout.
--
Yaakov
--
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
next prev parent reply other threads:[~2016-05-16 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-16 15:42 Warren Young
2016-05-16 16:50 ` Andrey Repin
2016-05-16 17:20 ` Warren Young
2016-05-16 17:50 ` Yaakov Selkowitz [this message]
2016-05-19 23:21 ` Hans-Bernhard Bröker
2016-05-20 1:20 ` Warren Young
2016-06-30 0:03 ` David Macek
[not found] ` <a62bb487-1a0c-77a0-ce29-09520dcbdb7b@gmail.com>
2016-07-01 9:30 ` Corinna Vinschen
2016-05-16 17:53 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4b37d689-285d-7dd4-3e3d-d40b4ee2f81f@cygwin.com \
--to=yselkowitz@cygwin.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).