Date: Sun, 21 May 2006 09:34:46 -0700
From: clayne AT anodized DOT com
To: cygwin AT cygwin DOT com
Subject: Re: GDB and Cygwin SIGSEGV revisited
Message-ID: <20060521163446.GA5748@ns1.anodized.com>
References: <002101c67cdb$6fbc6ee0$6702000a AT BLUESEA> <447075DC DOT FC1AAE93 AT dessent DOT net>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <447075DC.FC1AAE93@dessent.net>
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 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:

1. mutex attribute type
2. thrad attribute type

results in a SIGSEGV.

mutex and condvars no longer result in a visible SIGSEGV with one of the newer
snapshots and 6.4. Also, I've found a better method which is:

handle SIGSEGV noprint nostop
handle SIGTRAP noprint nostop

Another method I've taken is to dynamically initialize all mutexes, attributes,
and condvars. But really I should have to do *any* of the above to debug code,
as they are mediocre solutions.

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