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: Fri, 14 Sep 2001 13:30:25 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Useful details about the Make SEGVs Message-ID: <20010914133025.F2709@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com 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> <20010914171959 DOT 5066 DOT qmail AT lizard DOT curl DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20010914171959.5066.qmail@lizard.curl.com> User-Agent: Mutt/1.3.21i On Fri, Sep 14, 2001 at 01:19:59PM -0400, Jonathan Kamens wrote: >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)? It will certainly hurt. I suspect it will probably also "just work" as is usually the case when debugging potential races with strace. It's probably worth a try, though. I would just strace each individual make run, though, overwriting the strace output file every time. Otherwise, you will fill up your hard disk. >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. See Egor's recent "how to" on debugging cygwin. It talks about how to do this. cgf