X-Spam-Check-By: sourceware.org Date: Sun, 21 May 2006 18:40:45 -0400 From: Christopher Faylor To: cygwin AT cygwin DOT com Subject: Re: GDB and Cygwin SIGSEGV revisited Message-ID: <20060521224045.GF26270@trixie.casa.cgf.cx> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <002101c67cdb$6fbc6ee0$6702000a AT BLUESEA> <447075DC DOT FC1AAE93 AT dessent DOT net> <20060521163446 DOT GA5748 AT ns1 DOT anodized DOT com> <20060521203918 DOT GB25090 AT trixie DOT casa DOT cgf DOT cx> <20060521223113 DOT GA13907 AT ns1 DOT anodized DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060521223113.GA13907@ns1.anodized.com> User-Agent: Mutt/1.5.11 Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 On Sun, May 21, 2006 at 03:31:13PM -0700, clayne AT anodized DOT com wrote: >On Sun, May 21, 2006 at 04:39:18PM -0400, Christopher Faylor wrote: >>>6.4 works, but I've found that no matter what, initializing the >>>following: >> >>There is no way that 6.4 is going to fix this problem since, as Brian >>noted, its release predates the fix that I checked in to deal with the >>problem. > >Then what changed which stopped me from seeing SIGSEGV signals with >later snapshots while changing nothing in my code? It did not stop ALL >of them, but it did stop the pthread_mutex_init() case ones. I don't know and I'm not particularly interested in debugging older versions of gdb. Again, Brian answered the question correctly. Building a 6.4 version of gdb is not going to solve this problem. cgf -- 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/