X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Tue, 25 Aug 2009 21:36:26 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: BitDefender again Message-ID: <20090826013626.GC9672@ednor.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.20 (2009-06-14) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Tue, Aug 25, 2009 at 08:09:52PM -0400, Michael Kairys wrote: >BitDefender AntiVirus 2009 and Cygwin got along fine, but when I upgraded to >2010 all my Cygwin-based apps started crashing. If I turn off their "Active >Virus Control" the problem goes away. > >They offer this advice: > >===================================== >There is an incompatibility between cygwin and BitDefender AVC (Behavioral >Scanner). > >I'm going to get a little bit technical here in order to explain in detail >what is happening : > >Unfortunately, cygwin1.dll has a hardcoded image loading base (0x61000000) >wich conflicts with one of the BitDefender AVC plugins injected into >processes for monitoring their behaviour. This sounds fishy to me. Cygwin does prefer to load at 0x61000000 but, to the best of my knowledge, there is only one thing in Cygwin that really cares about this and it is not crucial to the operation of the DLL. cgf -- 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