From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH] Cygwin: ldd: Also look for not found DLLs when exit status is non-zero
Date: Fri, 11 Sep 2020 16:08:47 +0200 [thread overview]
Message-ID: <20200911140847.GL4127@calimero.vinschen.de> (raw)
In-Reply-To: <50e65d21-e501-99fe-80ef-e3b9c04bb4ed@dronecode.org.uk>
On Sep 11 13:33, Jon Turney wrote:
> On 10/09/2020 15:04, Corinna Vinschen wrote:
> > On Sep 10 13:27, Jon Turney wrote:
> > > If the process exited with e.g. STATUS_DLL_NOT_FOUND, also process the
> > > file to look for not found DLLs.
> > >
> > > (We currently only do this when a STATUS_DLL_NOT_FOUND exception occurs,
> > > which I haven't managed to observe)
> > >
> > > This still isn't 100% correct, as it only examines the specified file
> > > for missing DLLs, not recursively on the DLLs it depends upon.
> >
> > Better than nothing?
>
> Well, except when people are misled when investigating problems because they
> assume the output is accurate. (e.g. [1])
>
> [1] https://cygwin.com/pipermail/cygwin/2020-September/246164.html
>
> I guess what's maybe needed is some indication that an error occurred and
> the output may be incomplete if the inferior process exited with a non-zero
> status. But not sure how we can do that while keeping the output compatible
> with linux ldd.
I assume there *may* occur an error in ldd as well, so it might be
intersting to check the Linux ldd sources to see how it generates
error output.
Corinna
prev parent reply other threads:[~2020-09-11 14:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 12:27 Jon Turney
2020-09-10 14:04 ` Corinna Vinschen
2020-09-11 12:33 ` Jon Turney
2020-09-11 14:08 ` Corinna Vinschen [this message]
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=20200911140847.GL4127@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).