public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: rodrigo@tekchile.cl
To: gdb@sources.redhat.com
Subject: problems with pthread library
Date: Fri, 05 Aug 2005 13:28:00 -0000	[thread overview]
Message-ID: <62291.12.151.136.254.1123248500.squirrel@www.tekchile.cl> (raw)

Hello group:



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.



Any hints on what is going on ?

Thanks,

Rodrigo.


             reply	other threads:[~2005-08-05 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-05 13:28 rodrigo [this message]
2005-08-05 14:26 ` Dave Korn
2005-08-08 13:45   ` Rodrigo Varas

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=62291.12.151.136.254.1123248500.squirrel@www.tekchile.cl \
    --to=rodrigo@tekchile.cl \
    --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).