This is the mail archive of the
cygwin@cygwin.com
mailing list for the Cygwin project.
RE: pthreads "problem" Re: GDB always receives sigsegv with cygwin 1.3.13-2
- From: "Rolf Campbell" <rcampbell at tropicnetworks dot com>
- To: <cygwin at cygwin dot com>
- Date: Wed, 16 Oct 2002 20:10:03 -0400
- Subject: RE: pthreads "problem" Re: GDB always receives sigsegv with cygwin 1.3.13-2
> -----Original Message-----
> From: Christopher Faylor [mailto:cgf@redhat.com]
> Sent: Wednesday, October 16, 2002 7:54 PM
>
> Ok. This is occurring in code compiled via gcc 3. gcc 3
> uses a phreads mutex which is assigned to
> PTHREAD_MUTEX_INITIALIZER. There is a check for whether the
> mutex pointer is valid or not. It isn't valid as a pointer
> but it is still a valid value. So, a "harmless" SIGSEGV
> occurs while checking the pointer. The program traps the
> SIGSEGV so you never see it but that is immaterial to gdb
> which dutifully reports it.
So, silly question, why did this only start appearing in this new
version of cygwin?
> So, in the command line at least, you will be able to just
> continue on.
Yeah, "cont" worked. It worked in the gui too, I just couldn't figure
out how to click the button labeled "Continue".
-Rolf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/