This is the mail archive of the
gdb-prs@sourceware.org
mailing list for the GDB project.
c++/1986: Problems with pthread library
- From: rodrigo at tekchile dot cl
- To: gdb-gnats at sources dot redhat dot com
- Date: 5 Aug 2005 13:07:54 -0000
- Subject: c++/1986: Problems with pthread library
- Reply-to: rodrigo at tekchile dot cl
>Number: 1986
>Category: c++
>Synopsis: Problems with pthread library
>Confidential: no
>Severity: critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Fri Aug 05 13:08:01 UTC 2005
>Closed-Date:
>Last-Modified:
>Originator: rodrigo@tekchile.cl
>Release: unknown-1.0
>Organization:
>Environment:
Windows XP SP2
>Description:
I'm begining to migrate a 10k lines of code project to use the GNU tools.
I'm using eclipse 3.1 & CDT + latest Cygwin.
I have rewrite the OS Layer to begin use pthread library for
multi-threading capabilites.
When i try to debug my program i note the CPU going almost 100% with my
program & gdb.exe taking most of it. The program never goes further.
If i run the program without the debugger everything goes well.
So i decided to investigate more and found where the program hangs.
I found that when creating mutexes the debugger get lost. Not after the
first call but after a couple of invocation of 'pthread_mutex_init' &
'pthread_cond_init'.
I can repro the similar problem without using eclipse but directly using
cygwin and gdb.
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: