This is the mail archive of the
cygwin-talk
mailing list for the cygwin project.
Re: FW: cygwin-1.dll long-time bug
- From: Christopher Faylor <cgf-no-personal-reply-please at cygwin dot com>
- To: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
- Date: Tue, 18 Apr 2006 14:25:47 -0400
- Subject: Re: FW: cygwin-1.dll long-time bug
- References: <002801c66313$d0d31260$a501a8c0@CAM.ARTIMI.COM>
- Reply-to: cygwin-talk at cygwin dot com
- Reply-to: The Cygwin-Talk Malingering List <cygwin-talk at cygwin dot com>
On Tue, Apr 18, 2006 at 07:13:38PM +0100, Dave Korn wrote:
>where Mark Russinovich says
>
>"As for the issues looking at threads, the problem is a Cygwin behavior
>that's incompatible with the Windows API,
>RtlQueryProcessDebugInformation, that Process Explorer uses to obtain
>the list of modules loaded into a process. That API injects a thread
>into the remote process to query the loader data structures. The
>target process DLLs get a DLL_THREAD_ATTACH notification, which causes
>some Cygwin DLL thread to hang and the RtlQueryProcessDebugInformation
>to never return."
So, rather than saying "I wonder why Cygwin would hang when a thread is
injected?" the conclusion is that "Cygwin behavior which is incompatible
with the Windows API" and the fix is to "thread injection gracefully".
I don't see what more there is to say on the subject. Clearly with just
a little more grace, Cygwin's problems would be solved.
cgf