From: Brian Inglis <Brian.Inglis@Shaw.ca>
To: cygwin-apps@cygwin.com
Cc: Rodney Brown <rbrown@bravurasolutions.com>
Subject: Re: x86_64 ldd hangs running on a DLL
Date: Mon, 22 May 2023 08:38:33 -0600 [thread overview]
Message-ID: <79bdd450-31a3-10c8-7f24-75716030c6b6@Shaw.ca> (raw)
In-Reply-To: <14b85c22-ce8f-457d-abf4-61efdc2b474f@dronecode.org.uk>
BLODA? https://cygwin.com/faq/faq.html#faq.using.bloda
On 2023-05-21 14:32, Jon Turney via Cygwin-apps wrote:
> On 18/05/2023 02:46, Rodney Brown via Cygwin wrote:
>> $ uname -a
>> CYGWIN_NT-10.0-19045 X 3.4.6-1.x86_64 2023-02-14 13:23 UTC x86_64 Cygwin
>> $ ldd --version
>> ldd (cygwin) 3.4.6
>>
>> As with "ldd freezes"
>> https://sourceware.org/legacy-ml/cygwin/2015-07/msg00314.html , cygcheck works,
>> not only for Cygwin DLLs and ldd hangs needing the xterm to be closed, though
>> it can interrupted when run
>> under strace, or did. Strace now is segfaulting.
>
> What changed to make it start segfaulting?
>
>> Did Corinna's fix for i686 not end up in the x86_64 code?
>
> The claim here seems to be: ldd is broken on x86_64 for all dlls, and has been
> since 2015, and nobody has noticed.
>
> While possible, this seems unlikely.
>
> All I can tell you is that it appears to WFM. Perhaps you can provide some more
> details?
>
>> $ ldd /usr/bin/cygwin1.dll
>> ntdll.dll => /cygdrive/c/WINDOWS/SYSTEM32/ntdll.dll (0x7ffe56090000)
>> KERNEL32.DLL => /cygdrive/c/WINDOWS/System32/KERNEL32.DLL
>> (0x7ffe54a90000)
>> KERNELBASE.dll => /cygdrive/c/WINDOWS/System32/KERNELBASE.dll
>> (0x7ffe53c40000)
>> msvcrt.dll => /cygdrive/c/WINDOWS/System32/msvcrt.dll (0x7ffe55750000)
>> advapi32.dll => /cygdrive/c/WINDOWS/System32/advapi32.dll
>> (0x7ffe54d90000)
>> sechost.dll => /cygdrive/c/WINDOWS/System32/sechost.dll (0x7ffe549b0000)
>> RPCRT4.dll => /cygdrive/c/WINDOWS/System32/RPCRT4.dll (0x7ffe55570000)
>> CRYPTBASE.DLL => /cygdrive/c/WINDOWS/SYSTEM32/CRYPTBASE.DLL
>> (0x7ffe53060000)
>> bcryptPrimitives.dll =>
>> /cygdrive/c/WINDOWS/System32/bcryptPrimitives.dll (0x7ffe53770000)
>
--
Take care. Thanks, Brian Inglis Calgary, Alberta, Canada
La perfection est atteinte Perfection is achieved
non pas lorsqu'il n'y a plus rien à ajouter not when there is no more to add
mais lorsqu'il n'y a plus rien à retirer but when there is no more to cut
-- Antoine de Saint-Exupéry
next prev parent reply other threads:[~2023-05-22 14:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d4a99ce6758d46298f15040e5e3f82ff@bravurasolutions.com>
2023-05-21 20:32 ` Jon Turney
2023-05-22 1:35 ` Rodney Brown
2023-05-22 14:38 ` Brian Inglis [this message]
2023-05-23 0:32 ` Rodney Brown
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=79bdd450-31a3-10c8-7f24-75716030c6b6@Shaw.ca \
--to=brian.inglis@shaw.ca \
--cc=cygwin-apps@cygwin.com \
--cc=rbrown@bravurasolutions.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).