This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
RE: problems with pthread library
- From: "Rodrigo Varas" <rodrigo at tekchile dot cl>
- To: "'Dave Korn'" <dave dot korn at artimi dot com>, <gdb at sources dot redhat dot com>
- Date: Mon, 8 Aug 2005 09:45:49 -0400
- Subject: RE: problems with pthread library
Hello Dave,
Thanks for your reply.
I can go back to a previous cygwin but how to explain that the application
start normally without any debugging involved ?
Rodrigo.
-----Original Message-----
From: Dave Korn [mailto:dave.korn@artimi.com]
Sent: Friday, August 05, 2005 10:26 AM
To: rodrigo@tekchile.cl; gdb@sources.redhat.com
Subject: RE: problems with pthread library
----Original Message----
>From: rodrigo
>Sent: 05 August 2005 14:28
> Hello group:
¡Hola! Rodrigo,
> I have rewrite the OS Layer to begin use pthread library for
> multi-threading capabilites.
> 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'.
> Any hints on what is going on ?
I think there is a bug in pthread_cond_* or pthread_mutex_* functionality
in cygwin at the moment. If you roll back your cygwin dll version to 1.5.17
(using the 'prev' button in the cygwin setup.exe), does that fix it?
cheers,
DaveK
--
Can't think of a witty .sigline today....