X-Recipient: archive-cygwin@delorie.com X-Spam-Check-By: sourceware.org Message-ID: <47FBE273.F390E790@dessent.net> Date: Tue, 08 Apr 2008 14:24:03 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: Question on gdb and ?? And also Frame did not save PC message References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Brian Keener wrote: > (gdb) set cygwin-exceptions on > (gdb) run > ... > Program received signal SIGSEGV, Segmentation fault. > 0x610d5de9 in pthread_mutexattr_init (attr=0x23cb50) > at /usr/develop/src/src/src/winsup/cygwin/thread.cc:123 > 123 if ((*object)->magic != magic) > (gdb) thread apply all bt Why are you setting cygwin-exceptions on? The SEGV you are seeing is normal and not an actual SEGV. That gdb setting was added specifically to keep people from seeing this exception and others like it and thinking that somehow there's a segmentation fault in pthreads code when there isn't. If you're going to enable the option then you need to "continue" past those non-faults. 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/