X-Spam-Check-By: sourceware.org
Date: Sun, 21 May 2006 16:39:18 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: GDB and Cygwin SIGSEGV revisited
Message-ID: <20060521203918.GB25090@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <002101c67cdb$6fbc6ee0$6702000a@BLUESEA> <447075DC.FC1AAE93@dessent.net> <20060521163446.GA5748@ns1.anodized.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20060521163446.GA5748@ns1.anodized.com>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Sun, May 21, 2006 at 09:34:46AM -0700, clayne@anodized.com wrote:
>On Sun, May 21, 2006 at 07:14:52AM -0700, Brian Dessent wrote:
>>Richard Schmitt wrote:
>>
>>>- downloaded the latest gdb (6.4), built it and installed it.  [...]
>>>doesn't suffer from this problem?  The issue was fixed in CVS earlier
>>>this year.  But do note that it requires functionality not present in
>>
>>6.4 won't do, it's too old.  The fix was committed in February 2006.
>>6.4 was released in December 2005.
>
>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.

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/

