This is the mail archive of the cygwin-patches mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Extend faq.using to discuss fork failures

From: Eric Blake <eblake at redhat dot com>
To: cygwin-patches at cygwin dot com
Date: Fri, 26 Aug 2011 08:07:43 -0600
Subject: Re: Extend faq.using to discuss fork failures
References: <4E570027.9050300@cs.utoronto.ca>

On 08/25/2011 08:08 PM, Ryan Johnson wrote:

Based on the feedback on cygwin-dev, I've put together a revised pair of faq.using entries: one listing briefly the symptoms of fork failures and what to do about it, and the other giving some details about why fork fails (sometimes in spite of everything we do to compensate).

+
+<listitem>DLL injection by BLODA. Badly-behaved applications which
+    inject dlls into other processes often manage to clobber important
+    sections of the child's address space, leading to base address
+    collisions which rebasing cannot fix.

I would suggest adding an <a href=> tag around BLODA, to point users to the list of known bad software.

--
Eric Blake   eblake@redhat.com    +1-801-349-2682
Libvirt virtualization library http://libvirt.org

References:
- Extend faq.using to discuss fork failures
  - From: Ryan Johnson

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]