Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <20011120141501.3557.qmail@web21007.mail.yahoo.com>
Date: Tue, 20 Nov 2001 06:15:01 -0800 (PST)
From: Evan Pollan <evan_pollan AT yahoo DOT com>
Subject: gdb for multi-threaded apps?
To: cygwin AT cygwin DOT com
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

All--

I'm trying to use gdb on a simple mt app (contradiction in terms, maybe...). 
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 an error message popup
announcing 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 final state of the "Source Display Status Bar:"

>>> (function:) _libkernel32_a_iname (display mode:) ASSEMBLY

Here's the final state of the "Source Display:"

>>>  Unable to Read Instructions at 0x77e86e74


thanks for the help,
Evan

__________________________________________________
Do You Yahoo!?
Yahoo! GeoCities - quick and easy web site hosting, just $8.95/month.
http://geocities.yahoo.com/ps/info1

--
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/