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 Delivered-To: mailing list cygwin AT cygwin DOT com Date: Thu, 10 Jan 2002 21:29:51 -0500 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: gcc version 2.95.3-5: assert() does not work as expected Message-ID: <20020111022951.GA3407@redhat.com> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <5 DOT 0 DOT 0 DOT 25 DOT 2 DOT 20020109120734 DOT 02038df0 AT aut DOT ethz DOT ch> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5.0.0.25.2.20020109120734.02038df0@aut.ethz.ch> User-Agent: Mutt/1.3.23.1i On Wed, Jan 09, 2002 at 12:17:52PM +0100, Torrisi Fabio wrote: >Dear maintainers, > >Please consider the following bug: > >Problem: >assert does not work as written in the manual > >symptom: >If I register a signal handler for SIGABRT it does not get called by assert Yes, that was definitely a problem. It's been around for a while too. Thanks for the test case. This is fixed in the sources and will be in in tonight's cygwin snapshot. cgf -- 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/