Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm 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 Date: Sun, 6 Feb 2005 15:23:56 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: hyperthreading fix, try #1 Message-ID: <20050206202356.GH13306@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com References: <20050206180824 DOT GA32126 AT trixie DOT casa DOT cgf DOT cx> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Sun, Feb 06, 2005 at 07:22:48PM +0100, Volker Bandke wrote: >I have started my test script about half an hour ago, and it is still >running. It never managed to do that before. This could be a good >sign. Now, the snapshot DLL is far larger than the standard dll (I >would ASSume because of debug info). Can the debugging info/additional >baggage that is being carried around influence the normal runtime >behaviour? Should I run strip against the snapshot DLL and rerun my >test? I've been building snapshots with debugging turned on lately, yes. I don't think it is possible for this to impact this problem. I certainly saw it with a non-stripped DLL. However, in the interests of science, it probably would be a good idea to strip the DLL and try again if you have time. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/