Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 4 Mar 2004 10:59:48 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: Snapshot 20040225: make hangs/errors out Message-ID: <20040304155948.GA21030@redhat.com> Mail-Followup-To: cygwin AT cygwin DOT com References: <403E72B7 DOT 9050305 AT scytek DOT de> <403FD3AC DOT 7010300 AT scytek DOT de> <4044E025 DOT 2060501 AT scytek DOT de> <20040302204752 DOT GA11909 AT redhat DOT com> <40451E42 DOT 4070806 AT scytek DOT de> <4044B845 DOT 7000003 AT scytek DOT de> <20040303033617 DOT GA5325 AT redhat DOT com> <20040304021428 DOT GA5815 AT redhat DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040304021428.GA5815@redhat.com> User-Agent: Mutt/1.4.1i Reply-To: cygwin AT cygwin DOT com On Wed, Mar 03, 2004 at 09:14:28PM -0500, Christopher Faylor wrote: >On Wed, Mar 03, 2004 at 06:16:55PM -0500, Rolf Campbell wrote: >>Christopher Faylor wrote: >>>>>No, but I'll try to catch one. (I removed the strace from my script.) >>>> >>>>Ok, caught two already. (Produced with attached script + Makefile) >>> >>>Not much to there, unfortunately. >>> >>>Out of curiousity, can you duplicate this problem with the snapshot? I >>>see that this is your own build, probably built with >>>--enable-debugging. >>> >>>I've been diligently testing things with the snapshot rather than my >>>own build because I was trying to debug what was in the subject. >>>Snapshots aren't built with --enable-debugging. If this is just an >>>artifact from building with --enable-debugging, then I'm not too >>>worried. >> >>Ok, I've been running the script with the '25 snapshot all day, with 44 >>failures. All the same type of failures I was seeing with the cvs >>(with --enable-debugging). Unfortunitely, the ethernet card on my home >>machine broke so for now I'll upload one of the strace files to a >>geocites site. Nothing looks suspicious to me in the strace, maybe >>it's a bug in make? http://www.geocities.com/endlisnis/Temp/freeze.zip > >Thanks. Unfortunately, I don't see anything more here than in the other >strace output. > >I did manage to duplicate this after 1437 repetitions or so. My strace >didn't show anything either, unfortunately, but now maybe I can slowly >get to the bottom of the problem. Weird. Now that I've managed to duplicate it, I can do so at will. I guess that's good news. I see what is causing the symptom but not what is causing the problem. I spent a sleepless night modelling multi-threaded signal interrupts in my head but I'm still not any closer to understanding the problem. The problem is that malloc allocates some memory, puts the address of the memory in the eax register, and then returns. In the meantime, two signals have come in, so rather than return immediately, malloc returns to the signal handler and then the signal handler is called again. In some cases, this causes the eax register to become zero and so make (rightly) complains. In theory, this shouldn't happen since the eax register should have been saved on the stack. Nope. Typing an explanation doesn't help me figure this out. Bummer. cgf -- 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/