Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com Date: Tue, 20 Mar 2001 16:27:19 +0300 From: Egor Duda X-Mailer: The Bat! (v1.45) Personal Reply-To: Egor Duda Organization: DEO X-Priority: 3 (Normal) Message-ID: <907012433.20010320162719@logos-m.ru> To: Christopher Faylor Subject: Re: State of the DLL, mark 2? In-reply-To: <20010319203650.A30559@redhat.com> References: <20010319203650 DOT A30559 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi! Tuesday, 20 March, 2001 Christopher Faylor cgf AT redhat DOT com wrote: CF> Ok, I think we've fixed the rxvt hanging problem. CF> I haven't heard any further feedback on the hangs during build problem. CF> Is Cygwin still misbehaving when building a sources.redhat.com toolchain? CF> I tried this the other day and things seemed to be working ok except CF> for the -mwin32 problems. i've stumbled over it just now. sh traps in free() -- someone's corrupting the heap :( it's 100% reproducible, and it's traps with 1.1.6 too. i'm rebuilding cygwin1.dll with MALLOC_DEBUG now. Hopefully, we'll see who's corrupting the heap. btw, how big is MALLOC_DEBUG's penalty on performace? perhaps we should enable this if configured with --enable-debugging? or add --enable-malloc-debugging? Egor. mailto:deo AT logos-m DOT ru ICQ 5165414 FidoNet 2:5020/496.19