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: Sat, 28 Jul 2001 10:57:06 -0400 From: Christopher Faylor To: cygwin-developers AT cygwin DOT com Subject: Re: Problems with autoconf-2.52 testsuite using current CVS Cygwin Message-ID: <20010728105706.C16125@redhat.com> Reply-To: cygwin-developers AT cygwin DOT com Mail-Followup-To: cygwin-developers AT cygwin DOT com References: <20010725173147 DOT P490 AT cygbert DOT vinschen DOT de> <005d01c1176f$19910e30$0300a8c0 AT ufo> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.11i In-Reply-To: <005d01c1176f$19910e30$0300a8c0@ufo>; from trevorforbes@ozemail.com.au on Sat, Jul 28, 2001 at 11:37:41PM +0930 On Sat, Jul 28, 2001 at 11:37:41PM +0930, Trevor Forbes wrote: >Things are a bit clearer now that there is no file name collisions. I think >the trap is not working all the time and therefore it is not calling >"rm"..... >trap 'exit_status=$?; rm -rf $tmp && exit $exit_status' 0 > >This is far as I have got, I am sort of stumped as to which direction to go >next. How do you debug this sort of signal problem?....... Anyway, I am >just reporting my finding so far just in case someone else can see the >solution. Note, I have not stopped looking into it... If the trap above is any indication, it's not a signal problem it's an "execute on exit" problem. I wonder if this is related to the "new" vfork stuff in ash. Maybe that's not properly calling exit handlers or something. cgf