Thrall, Bryan wrote on Monday, May 04, 2009 10:36 AM:
> Christopher Faylor wrote on Monday, May 04, 2009 10:18 AM:
>> cygcheck itself would not be redoing anything because 1) it isn't a
true
>> cygwin program and 2) it isn't starting a process when it displays
dll
>> information.
>
> Unfortunately, unless I'm doing something wrong, it isn't due to
> proc_retry:
I was doing something wrong; you need to set proc_retry before the
Cygwin DLL is loaded; after doing that, I do only get one copy of the
output from 'cygcheck /bin/ash.exe -v'. It still returns 127, though:
thr...@pc1163-8413-xp ~
$ cygcheck /bin/ash.exe -v
C:\cygwin_1.7\bin\ash.exe
C:\cygwin_1.7\bin\cygwin1.dll
C:\WINDOWS\system32\ADVAPI32.DLL
C:\WINDOWS\system32\ntdll.dll
C:\WINDOWS\system32\KERNEL32.dll
C:\WINDOWS\system32\RPCRT4.dll
thr...@pc1163-8413-xp ~
$ echo $?
127
--
Bryan Thrall
FlightSafety International
bryan.thr...@flightsafety.com
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
