This is the mail archive of the
cygwin
mailing list for the Cygwin project.
Re: Question on gdb and ?? And also Frame did not save PC message
- From: Brian Dessent <brian at dessent dot net>
- To: cygwin at cygwin dot com
- Date: Tue, 08 Apr 2008 14:24:03 -0700
- Subject: Re: Question on gdb and ?? And also Frame did not save PC message
- References: <VA.000017a9.0052f369@thesoftwaresource.com>
- Reply-to: cygwin at cygwin dot 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/