On 20. 5. 2016 3:20, Warren Young wrote: > On May 19, 2016, at 5:21 PM, Hans-Bernhard Bröker <hbbroe...@t-online.de> > wrote: >> >> Does not WFM: > > [snip] > >> This is with ldd.exe from cygwin-2.5.1-1, on Win10 64bit, installed into >> c:\cygwin64
Just bumped into this as well.
Win10 64bit (1607 build 14367) with MSYS2 64bit:
$ ldd /usr/bin/ls
ntdll.dll => /c/WINDOWS/SYSTEM32/ntdll.dll (0x7fff19e60000)
KERNEL32.DLL => /c/WINDOWS/System32/KERNEL32.DLL (0x7fff198a0000)
KERNELBASE.dll => /c/WINDOWS/System32/KERNELBASE.dll (0x7fff17240000)
Win8.x 64bit with MSYS2 64bit:
$ ldd /usr/bin/ls
ntdll.dll => /c/Windows/SYSTEM32/ntdll.dll (0x7ffda3810000)
KERNEL32.DLL => /c/Windows/system32/KERNEL32.DLL (0x7ffda3310000)
KERNELBASE.dll => /c/Windows/system32/KERNELBASE.dll (0x7ffda0d80000)
msys-intl-8.dll => /usr/bin/msys-intl-8.dll (0x430b30000)
msys-2.0.dll => /usr/bin/msys-2.0.dll (0x180040000)
msys-iconv-2.dll => /usr/bin/msys-iconv-2.dll (0x3ff760000)
Both installations are up to date and should have identical binaries.
Looking into procmon, the only relevant difference I see is `sysmain.sdb` being
checked right after `ls.exe` process creation, but that could very well be a
red herring. Unfortunately, ACT seems to be broken on Win10.
I can try watching them side by side in debuggers tomorrow, maybe I'll find
something.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
