X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org To: cygwin@cygwin.com From: Matthew Woehlke Subject: Re: Help needed with Big List of Dodgy Apps Date: Fri, 07 Sep 2007 16:17:30 -0500 Lines: 15 Message-ID: References: <20070907175712.GA8852@ednor.casa.cgf.cx> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.6) Gecko/20070728 Thunderbird/2.0.0.6 Mnenhy/0.7.5.0 In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Robert Kiesling wrote: >> ? I don't know what this means but Windows has the equivalent of SIGSEGV. > > The signal is non-catchable by UNIX apps. That ability would > be useful when malloc goes whizzing off into the video RAM, but > the issue is almost always a bug somewhere else in the app. That > is not to say that the system libraries are perfect, of course. Um... I can catch SIGSEGV just fine in my UNIX apps. Or did you mean cygwin apps can't catch it? (Granted, I don't attempt to *recover* from a SEGV, just say "hey, I got a SEGV" and either exit() or abort().) -- Matthew Cannot read .sig now -- 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/