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: 14 Sep 2001 13:19:59 -0400 Message-ID: <20010914171959.5066.qmail@lizard.curl.com> From: Jonathan Kamens To: cygwin-developers AT cygwin DOT com CC: cygwin-developers AT cygwin DOT com In-reply-to: <20010914131117.D2709@redhat.com> (message from Christopher Faylor on Fri, 14 Sep 2001 13:11:17 -0400) Subject: Re: Useful details about the Make SEGVs References: <20010912173945 DOT 25925 DOT qmail AT lizard DOT curl DOT com> <20010914002450 DOT B25486 AT redhat DOT com> <20010914170318 DOT 4862 DOT qmail AT lizard DOT curl DOT com> <20010914131117 DOT D2709 AT redhat DOT com> Do you think I should try rerunning the "make -j2" under strace? How about running it with a cygwin1.dll compiled with malloc debugging (ouch! that'll hurt)? Incidentally, is it possible to run an application using a cygwin1.dll with malloc debugging but to run gdb on the application using a cygwin1.dll *without* malloc debugging? Gdb seems very difficult to use when malloc debugging is enabled. jik