All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: "Landau, Bracha" <BLandau@domain.hid>
Cc: xenomai@xenomai.org
Subject: RE: [Xenomai-help] pthread_mutex_destroy in 2.2 rc2
Date: Sun, 2 Jul 2006 17:35:17 +0200	[thread overview]
Message-ID: <17575.59317.183222.418817@domain.hid> (raw)
In-Reply-To: <02AA386EB831044F8537A696BA785C78A66770@domain.hid>

Landau, Bracha wrote:
 > As you suggested, I've upgraded to xenomai 2.2 rc3.
 > I still see the same phenomenon.
 > I'm attaching code that will reproduce the error.
 > (When you ^c out of the main loop, the pthread_cleanup_pop is called, and the call to pthread_mutex_destroy returns 0x10.)

I did not make myself clear... 

I did not meant that 2.2 rc3 would solve your issue, simply that it has
automatic per-process cleanup, so, it does not matter if your
application fail to destroy some condition variables, the condition
variable is destroyed automatically anyway. It is simpler for you to
work with this version as long as the bug you met is not solved.

As for the pthread_cleanup_push/pthread_cleanup_pop, it was meant to be
the solution if the EBUSY had been due to a thread blocked in a call to
pthread_cond_wait during the application cleanup.

I have a look at your code.


-- 


					    Gilles Chanteperdrix.


  reply	other threads:[~2006-07-02 15:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-02 13:43 [Xenomai-help] pthread_mutex_destroy in 2.2 rc2 Landau, Bracha
2006-07-02 15:35 ` Gilles Chanteperdrix [this message]
2006-07-03 13:15 ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2006-07-03 15:26 Landau, Bracha
2006-06-29 15:36 Landau, Bracha
2006-06-29 16:16 ` Gilles Chanteperdrix

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=17575.59317.183222.418817@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=BLandau@domain.hid \
    --cc=xenomai@xenomai.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.