I've seen a lot of discussion on issues with SIGSEGV and pthread mutexes with GDB under cygwin. I was very hopeful when I saw a reply by Brian Dessent that said this was fixed if I downloaded the latest gdb and a cygwin snapshot. Maybe there's something else I haven't downloaded but here's what I did, and I still have the problem. - ran cygwin's setup and updated my installation - downloaded the latest cygwin snapshot cygwin1-20060521.dll.bz2 - unzipped the cygwin snapshot, renamed it cygwin1.dll and placed in in /usr/bin - downloaded the latest gdb (6.4), built it and installed it. - tried to debug my program. What I get is: GNU gdb 6.4 Copyright 2005 Free Software Foundation, Inc. ... Program received signal SIGSEGV, Segmentation fault. 0x610b0fc5 in pthread_mutexattr_init () from /usr/bin/cygwin1.dll (gdb) Curiously, if I issue the following to GDB as others have suggested:
handle SIGSEGV nostop handle SIGTRAP nostop I will get continuous and unrelenting messages: Program received signal SIGSEGV, Segmentation fault. Is there a later or different snapshot of cygwin we should use, or a different GDB? Any help will be greatly appreciated. Rich * From: Brian Dessent <brian at dessent dot net> * To: cygwin at cygwin dot com * Date: Mon, 08 May 2006 02:01:00 -0700 * Subject: Re: pthread_mutex_init + gdb issue again * References: <[EMAIL PROTECTED] <http://sourceware.org/ml/cygwin/2006-05/msg00139.html> > * Reply-to: cygwin at cygwin dot com ________________________________ [EMAIL PROTECTED] wrote: > Someone throw me a bone here, please. Rather than work-arounds, why not just use a recent build of gdb that 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 Cygwin 1.5.19, so you'll also need to use a recent Cygwin snapshot. 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/
