Re: Patch to allow CVS cygwin enable-malloc-debugging to compile

On Fri, Jun 13, 2003 at 02:20:47PM -0500, Michael Checky wrote: >On Thu, 12 Jun 2003, Christopher Faylor wrote: >> 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. > >I didn't s

Re: Patch to allow CVS cygwin enable-malloc-debugging to compile

On Thu, 12 Jun 2003, Christopher Faylor wrote: > 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. I didn't submit the patch to be applied to the cygwin sources, I submitted it to

Re: Patch to allow CVS cygwin enable-malloc-debugging to compile

I would except for the fact that the web page also states you can't post to [EMAIL PROTECTED] unless you subscribe to it. I'm not interested in subscribing. Feel free to cross-post the patch if you want. Michael Checky You might want to send this to [EMAIL PROTECTED] , as per

Re: Patch to allow CVS cygwin enable-malloc-debugging to compile

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 th

Re: Patch to allow CVS cygwin enable-malloc-debugging to compile

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