On Fri, Feb 24, 2012 at 03:42:33PM -0500, Christopher Faylor wrote: >On Thu, Feb 23, 2012 at 03:03:40PM -0800, cppjavaperl wrote: >>This was discovered in cygwin-1.7.10-1. >> >>If you run 'ldd' against an executable, and the executable has >>dependent DLLs which do *not* have execute permissions, ldd's output >>stops when it reaches the offending dependent DLL, and reports no >>further information.? ldd does not give an error message, and the exit >>code is zero. >> >>To test, pick an application with a dependent DLL, then chmod 666 on >>that DLL (pick a DLL you can live without temporarily, of course), then >>run 'ldd' against the executable. > >Can't reproduce this (with the latest DLL from the snapshot): > >bash$ chmod a-w /bin/*.dll >bash$ ldd /bin/pwd > ntdll.dll => /cygdrive/c/Windows/SysWOW64/ntdll.dll (0x779a0000) > kernel32.dll => /cygdrive/c/Windows/syswow64/kernel32.dll (0x75310000) > KERNELBASE.dll => /cygdrive/c/Windows/syswow64/KERNELBASE.dll > (0x75ae0000) > cygwin1.dll => /usr/bin/cygwin1.dll (0x61000000) > cygintl-8.dll => /usr/bin/cygintl-8.dll (0x61730000) > cygiconv-2.dll => /usr/bin/cygiconv-2.dll (0x63c10000) > >Given how ldd works, it's hard to see why executable permissions should >affect it. ldd starts the executable for debugging and tracks .dlls as >they are loaded. The executable bit state should have no effect on >that.
Nevermind. Obviously I typoed the a-w and, so, my test is not going to do anything. Corinna's answer is the correct one. Sorry for the noise. cgf -- 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