Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com From: "Evan Pollan" To: Subject: Segmentation fault when using gdb & pthreads Date: Thu, 6 Dec 2001 22:23:53 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 Importance: Normal All-- I posted this a few weeks back and didn't get any response. I've searched the 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 wanted 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 everything up to the pthreads code. Is this a limitation w/ gdb or am I missing either a 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() call: (gdb) run Starting program: /cygdrive/c/home/Evan/src/c++/QueueProcessor/Driver.exe Breakpoint 1, QueueProcessor::QueueProcessor (this=0x22fd54) at QueueProcessor.cpp:39 39 { Current language: auto; currently c++ (gdb) step 41 rc = pthread_cond_init(&_condition, NULL); (gdb) print rc $1 = 0 (gdb) step Program received signal SIGSEGV, Segmentation fault. 0x77e86e72 in _libkernel32_a_iname () (gdb) thanks for the help, Evan _________________________________________________________ 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 Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/