From: "Rodrigo Varas" <rodrigo@tekchile.cl>
To: "'Dave Korn'" <dave.korn@artimi.com>, <gdb@sources.redhat.com>
Subject: RE: problems with pthread library
Date: Mon, 08 Aug 2005 13:45:00 -0000 [thread overview]
Message-ID: <007601c59c1f$7dd29880$3682a8c0@rvaraspclaptop> (raw)
In-Reply-To: <SERRANOwwjHGdG3ON4w000000c7@SERRANO.CAM.ARTIMI.COM>
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....
prev parent reply other threads:[~2005-08-08 13:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-05 13:28 rodrigo
2005-08-05 14:26 ` Dave Korn
2005-08-08 13:45 ` Rodrigo Varas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='007601c59c1f$7dd29880$3682a8c0@rvaraspclaptop' \
--to=rodrigo@tekchile.cl \
--cc=dave.korn@artimi.com \
--cc=gdb@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).