From: "Chris Friesen" <cfriesen@nortel.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linuxppc-dev@ozlabs.org, tglx@linutronix.de,
linux-kernel@vger.kernel.org
Subject: Re: BUG? timer_create() with SIGEV_THREAD not working (at least on ppc64)
Date: Tue, 18 Nov 2008 17:06:33 -0600 [thread overview]
Message-ID: <49234A79.8070707@nortel.com> (raw)
In-Reply-To: <492326B5.10203@nortel.com>
Chris Friesen wrote:
> I'm getting suspicious of either glibc or my version of strace, as it
> shows the child thread calling rt_sigtimedwait() with an empty signal set.
Looks like glibc was the culprit. It works fine with a newer version.
Sorry for the false alarm.
Chris
WARNING: multiple messages have this Message-ID (diff)
From: "Chris Friesen" <cfriesen@nortel.com>
To: "Chris Friesen" <cfriesen@nortel.com>
Cc: linuxppc-dev@ozlabs.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de
Subject: Re: BUG? timer_create() with SIGEV_THREAD not working (at least on ppc64)
Date: Tue, 18 Nov 2008 17:06:33 -0600 [thread overview]
Message-ID: <49234A79.8070707@nortel.com> (raw)
In-Reply-To: <492326B5.10203@nortel.com>
Chris Friesen wrote:
> I'm getting suspicious of either glibc or my version of strace, as it
> shows the child thread calling rt_sigtimedwait() with an empty signal set.
Looks like glibc was the culprit. It works fine with a newer version.
Sorry for the false alarm.
Chris
next prev parent reply other threads:[~2008-11-18 23:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-18 16:14 BUG? timer_create() with SIGEV_THREAD not working (at least on ppc64) Chris Friesen
2008-11-18 16:14 ` Chris Friesen
2008-11-18 20:33 ` Chris Friesen
2008-11-18 20:33 ` Chris Friesen
2008-11-18 23:06 ` Chris Friesen [this message]
2008-11-18 23:06 ` Chris Friesen
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=49234A79.8070707@nortel.com \
--to=cfriesen@nortel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=tglx@linutronix.de \
/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.