BLODA detection (was Re: Debugging help for fork failure: resource temporarily unavailable)

[ht@inf.ed.ac.uk (Henry S. Thompson)]

Ryan Johnson writes:

> BTW, I found a good way to identify, if not fix, BLODA: given an app
> which loads no libraries at runtime -- such as 'ls' -- any dlls
> mentioned in /proc/$$/maps which cygcheck does not mention are
> probably dodgy. In my case, Windows Live (which I didn't think was
> even installed on my machine) has injected a WLIDNSP.DLL ("Microsoft
> Windows Live ID Namespace Provider") in all my processes.

This would be super-cool if true, but it doesn't work for me. . .

If I try, I find

 C:\Windows\system32\ntmarta.dll
 C:\Windows\SysWOW64\sechost.dll
 C:\Windows\syswow64\WLDAP32.dll

in /proc/[ls procid]/maps but not in cygcheck output, but none of
those are BLODA, right?

[Note also that maps shows many things in syswow64 which cygcheck
shows in system32, but presumably that's because cygcheck itself is a
32-bit app, is it?]

ht
-- 
       Henry S. Thompson, School of Informatics, University of Edinburgh
      10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440
                Fax: (44) 131 651-1426, e-mail: ht@inf.ed.ac.uk
                       URL: http://www.ltg.ed.ac.uk/~ht/
 [mail from me _always_ has a .sig like this -- mail without it is forged spam]

--
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