This is the mail archive of the
mailing list for the Cygwin project.
Segmentation fault when using gdb & pthreads
- From: "Evan Pollan" <evan_pollan at yahoo dot com>
- To: <cygwin at cygwin dot com>
- Date: Thu, 6 Dec 2001 22:23:53 -0500
- Subject: Segmentation fault when using gdb & pthreads
I posted this a few weeks back and didn't get any response. I've searched
archives and haven't seen anything helpful, so I'm reposting...
I'm trying to use gdb on a simple pthreads app. The app runs fine, but I
to give the gdb a test drive. However, whenever I step into or over any
pthread code, I get a segmentation fault. In my case, a call to
pthread_cond_init() causes the SIGSEGV.
The code is compiled w/ -g, and I can step through the execution for
up to the pthreads code. Is this a limitation w/ gdb or am I missing either
compilation or debugging flag? I'm using the full cygwin distribution as of
cygwin-1.3.5-3 on Win2000.
Here's the seg fault as it appears when I encounter the pthread_cond_init()
Breakpoint 1, QueueProcessor::QueueProcessor (this=0x22fd54)
Current language: auto; currently c++
41 rc = pthread_cond_init(&_condition, NULL);
(gdb) print rc
$1 = 0
Program received signal SIGSEGV, Segmentation fault.
0x77e86e72 in _libkernel32_a_iname ()
thanks for the help,
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html