X-Recipient: archive-cygwin AT delorie DOT com DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; q=dns; s= default; b=iiih/53Ko1SNXFboTWCrmxoX7mVeaXRk+ZJ9vXZ6TL9mdN9RAxuD7 Fcb969hzAxRotsfuRnLhtGqHDGa4fA6HW7YlvQeKeR80+g0Tkg7ueLNhe3EnkOaQ K8vGOTAdnbznJu88DbmGSiHFjPvK5+byP6X0wKapSIXfdbAtN00lbI= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=sourceware.org; h=list-id :list-unsubscribe:list-subscribe:list-archive:list-post :list-help:sender:date:from:to:subject:message-id:reply-to :references:mime-version:content-type:in-reply-to; s=default; bh=RO6Pe9hubHwIrI/QAg1WcEGDcXk=; b=Cfox1ghVV3eSa9KvtqM3FxBjrLhE 1T4aAPS9YQ45/Y59RwgNAHqKwjwwbMCo7Pf3effzgNdGP6SG2hZ2l10QWFTZYnNV buIG4Tv5ZchlJ7CzWsN5zhnIUr3SVTaBKYcOo3uiA9yGvIilbpsB59andgbufrK9 UF8PmSjA69t2FQ8= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com X-Spam-SWARE-Status: No, score=0.2 required=5.0 tests=AWL,BAYES_50,RDNS_NONE autolearn=no version=3.3.1 Date: Mon, 29 Jul 2013 15:42:16 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: child (xterm) fork failure as it loads to different address Message-ID: <20130729134216.GA4166@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <51F65369 DOT 9020001 AT gmail DOT com> <51F66FB9 DOT 6000802 AT cs DOT utoronto DOT ca> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <51F66FB9.6000802@cs.utoronto.ca> User-Agent: Mutt/1.5.21 (2010-09-15) On Jul 29 09:35, Ryan Johnson wrote: > http://cygwin.com/acronyms/#TOFU > > On 29/07/2013 8:15 AM, Ariel Burbaickij wrote: > >OK, thank, you, so usual suspects. Now, removing, antivirus and stuff > >will not be possible in this particular environment but adjustments in > >the configuration are well possible, provided I will be able to prove > >to administrators that troubles, indeed, stem from antivirus and co. > >Now, I see in the FAQ in 4.42 section that these troubles were traced > >and attributed to antiviri programs. Any more details about how they > >were traced exactly, so that I can re-trace them too and provide a > >proof, if needed? > The proof usually goes something like this: > > 1. People report fork() failures on the list, and a correlation is > noted between those failures and presence of app/antivirus X. > 2. It is confirmed (or at least considered highly probable) that X > performs dll injection, the root cause of these sorts of fork() > failures. > 3. Somebody tries disabling/removing X and the fork() failures go away. > 4. X gets added to BLODA and reports of fork() failures, not > attributable to X, disappear from the list. > > Eventually the process repeats when Y appears. There's no Y. The successor of X is allegedly called Wayland. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Maintainer cygwin AT cygwin DOT com Red Hat -- 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