public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Bastian Voigt <bastian@voigt.in-berlin.de>
To: pthreads-win32@sources.redhat.com
Subject: calling mutex_lock() twice from one thread
Date: Mon, 15 Nov 2004 10:47:00 -0000	[thread overview]
Message-ID: <419888D2.3060502@voigt.in-berlin.de> (raw)

Dear list,

according to the documentation pthread_mutex_lock() assigns the mutex to 
the calling thread, and if a different thread calls it again it will be 
blocked.

In my scenario I want one thread to block itself, to be waked up later 
by a signal handler. This does not work by simply calling mutex_lock() 
twice, it does not block.

What can you recommend to achieve this? To be more concrete, I do the 
following:

The main thread loads some configuration, then starts some worker 
threads. After the worker threads are running I want the main thread to 
sleep until a signal (Ctrl-C) arrives. Will it work better when using 
semaphores?

Thanks for any hints!

Bastian Voigt

             reply	other threads:[~2004-11-15 10:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-15 10:47 Bastian Voigt [this message]
2004-11-15 11:09 ` Nicolas EDEL
2004-11-17  6:11 ` Will Bryant
2004-11-17  7:51   ` Bastian Voigt

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=419888D2.3060502@voigt.in-berlin.de \
    --to=bastian@voigt.in-berlin.de \
    --cc=pthreads-win32@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).