From: "René Berber" <rene.berber@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Question about the ldd output
Date: Tue, 09 Jul 2019 17:39:00 -0000 [thread overview]
Message-ID: <40138a18-4360-cd52-9eb9-7c32838ea9c8@gmail.com> (raw)
In-Reply-To: <ee7608a2-2e13-d2eb-6410-c07362d75296@SystematicSw.ab.ca>
On 7/9/2019 11:40 AM, Brian Inglis wrote:
> 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.
True, its just the way Windows works, some libraries are dynamically
loaded, some may not exist, and are not needed.
Try the view from SysInternals' Dependency Walker (which now seems to be
named ListDLLs, or maybe was added to ProcessExplorer), shows the same
thing (if the Windows PATH is set to include Cygwin's libraries), with
lots of interrogation signs... except that it also shows exactly which
dll is "missing".
--
R.Berber
--
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:[~2019-07-09 17:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 20:13 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-09 16:40 ` Brian Inglis
2019-07-09 17:39 ` René Berber [this message]
2019-07-09 18:02 ` Jon Turney
2019-07-10 22:55 ` Brian Inglis
2019-07-17 2:38 ` Mark Geisert
-- strict thread matches above, loose matches on Subject: below --
2019-07-08 21:07 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-05 18:28 Lavrentiev, Anton (NIH/NLM/NCBI) [C] via cygwin
2019-07-06 6:45 ` Brian Inglis
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=40138a18-4360-cd52-9eb9-7c32838ea9c8@gmail.com \
--to=rene.berber@gmail.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).