public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bugdal at aerifal dot cx" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug nptl/14484] sem_timedwait always return -1 with errno 110 (ETIMEDOUT).
Date: Tue, 21 Aug 2012 13:15:00 -0000	[thread overview]
Message-ID: <bug-14484-131-PXxJekklWU@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-14484-131@http.sourceware.org/bugzilla/>

http://sourceware.org/bugzilla/show_bug.cgi?id=14484

--- Comment #7 from Rich Felker <bugdal at aerifal dot cx> 2012-08-21 13:15:03 UTC ---
Your signal handler is not installed to be interrupting, so if sem_timedwait
returns with EINTR (which it _DOES_ do on some/most Linux versions), that's a
bug in the kernel. The expected result is ETIMEDOUT.

Perhaps you expect signal() to have the legacy sysv behavior of installing
interrupting signal handlers. This is not the case on glibc. If you want
interrupting behavior, you must use sigaction() and omit the SA_RESTART flag.

I still don't see any bug.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


  parent reply	other threads:[~2012-08-21 13:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-17  5:20 [Bug nptl/14484] New: " tingw.liu at gmail dot com
2012-08-17  6:08 ` [Bug nptl/14484] " bugdal at aerifal dot cx
2012-08-17  6:21 ` tingw.liu at gmail dot com
2012-08-17  6:26 ` tingw.liu at gmail dot com
2012-08-17  6:31 ` tingw.liu at gmail dot com
2012-08-20  1:41 ` bugdal at aerifal dot cx
2012-08-21  6:07 ` tingw.liu at gmail dot com
2012-08-21 13:15 ` bugdal at aerifal dot cx [this message]
2012-08-22  0:33 ` tingw.liu at gmail dot com
2012-08-22  0:34 ` tingw.liu at gmail dot com
2012-08-22  1:08 ` bugdal at aerifal dot cx
2012-08-22  5:21 ` tingw.liu at gmail dot com
2012-08-22  5:24 ` tingw.liu at gmail dot com
2012-08-22  5:29 ` tingw.liu at gmail dot com
2013-01-09 16:31 ` schwab@linux-m68k.org
2013-01-10  5:03 ` tingw.liu at gmail dot com
2013-01-10  5:03 ` tingw.liu at gmail dot com
2014-06-17 18:36 ` fweimer at redhat dot com
2014-06-17 18:56 ` bugdal at aerifal dot cx

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=bug-14484-131-PXxJekklWU@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).