From: "Joël Krähemann" <joel@weedlight.ch>
To: linux-rt-users@vger.kernel.org
Subject: Re: BUG - pthread conditional locks and barriers not reliable
Date: Fri, 29 Mar 2013 02:31:25 +0100 [thread overview]
Message-ID: <1364520685.8268.2.camel@debian> (raw)
In-Reply-To: <1364458931.4931.8.camel@debian>
Hi, just ignore the spam it was just a programming mistake.
Am Donnerstag, den 28.03.2013, 09:22 +0100 schrieb Joël Krähemann:
> Hi, I believe that pthread conditional locks and barriers aren't
> reliable. May be it's a problem with the kernel I just downloaded libc6
> to get an entry point.
>
> The code is located at: sf.org/p/ags
> affected files: src/ags/audio/ags_devout.c
>
> I've attached the output of lspci and lscpu.
>
>
> cu
> Joël
>
--
To unsubscribe from this list: send the line "unsubscribe linux-rt-users" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2013-03-29 1:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-28 8:22 BUG - pthread conditional locks and barriers not reliable Joël Krähemann
2013-03-29 1:31 ` Joël Krähemann [this message]
2013-03-29 1:49 ` Joël Krähemann
2013-04-08 6:20 ` Nicholas Mc Guire
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=1364520685.8268.2.camel@debian \
--to=joel@weedlight.ch \
--cc=linux-rt-users@vger.kernel.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 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 NNTP newsgroup(s).