Date: Sun, 21 May 2006 15:31:13 -0700
From: clayne AT anodized DOT com
To: cygwin AT cygwin DOT com
Subject: Re: GDB and Cygwin SIGSEGV revisited
Message-ID: <20060521223113.GA13907@ns1.anodized.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>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060521203918.GB25090@trixie.casa.cgf.cx>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

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.

-cl

--
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/