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 Message-ID: <007b01c2b8c3$e8ebdba0$2a49893e@POMELLO> From: "Max Bowsher" To: "Lapo Luchini" , "Mailing List: CygWin" References: <3E1EE1FB DOT 30704 AT lapo DOT it> Subject: Re: ^C => assertion failed in sigproc.cc Date: Fri, 10 Jan 2003 15:46:29 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Lapo Luchini wrote: > If I press ^C during a "make" or even a simple bash script I usually > get lots of (this is fairly 'new', never seen them before): > > assertion "!wait_sig_inited" failed: file > "/netrel/src/cygwin-1.3.17-1/winsup/cygwin/sigproc.cc", line 538 > > I see also that "uname -a" says me its 1.3.17, strangely... I > installed > 1.3.18 yesterday and, as always, I closed services and programs before > doing it. > > (Robert, is that 'patch' to avoid 'putting files into the reboot > queue' still in the CVS? can I compile myself a setup.exe that does > have it? ^_^) Current snapshot will respond to this command line option: -r --no-replaceonreboot Disable replacing in-use files on next reboot. NB this is a debug option. With it, setup will just fail to unpack the relevant file. You may be better off inspecting the rename queue and manually clearing it. Max. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/