X-Spam-Check-By: sourceware.org Message-ID: <44743861.AC6AFBF@dessent.net> Date: Wed, 24 May 2006 03:41:37 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: 1.5.19: changes have broken Qt3 References: <044e01c67e8f$0abed720$a501a8c0@CAM.ARTIMI.COM> <447350C4.1080604@freenet.de> <20060523182326.GB6138@trixie.casa.cgf.cx> <4473607C.2070806@freenet.de> <44741E31.665A1B7@dessent.net> <20060524100500.GK13907@ns1.anodized.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm 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 clayne@anodized.com wrote: > Actually, is this really a fault in gdb? Cygwin is throwing a SIGSEGV signal, > correct? GDB does what it's told, stops on SIGSEGV by default. Not really. In cases where it is checking parameters or otherwise expects to dereference an invalid pointer, Cygwin installs a temporary fault handler that intercepts any fault and returns the correct error code. If you run such code outside of gdb you get no indication of a fault at all, just like a standard try/except block -- unlike an actual segmentation violation where the program is terminated. So yes, it is a defect that gdb treats these as actual SIGSEGVs when they are actually just part of how Cygwin works internally, and this misperception has caused countless messages posted to this list insisting that there is some kind of problem in Cygwin where there is none. Brian -- 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/