Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Thu, 12 Jun 2003 22:06:55 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: Patch to allow CVS cygwin enable-malloc-debugging to compile Message-ID: <20030613020655.GA7645@redhat.com> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i On Fri, Jun 13, 2003 at 02:45:56AM +0100, Elfyn McBratney wrote: >On Thu, 12 Jun 2003, Michael Checky wrote: > >> I needed to enable malloc debugging to track down a memory corruption >> error. I had to apply this patch to get the CVS version of cygwin to >> compile after running configure with the --enable-malloc-debugging option. >> I didn't do any tests of the dll, but it seemed to work well enough to >> allow me to track down the bug. In case anybody is interested, I've >> tracked the memory bug it to either arm-elf-gcc 3.3 or arm-elf-ld 2.13.2.1. > >You might want to send this to cygwin-patches@cygwin.com , as per >. Don't bother. This patch is unacceptable for cygwin. Randomly adding '#if 0' to a header and '#ifndef __CYGWIN__' to cygwin code is not ever going to be accepted. -- Please use the resources at cygwin.com rather than sending personal email. Special for spam email harvesters: send email to aaaspam@sourceware.org and be permanently blocked from mailing lists at sources.redhat.com -- 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/