This is the mail archive of the
glibc-bugs@sourceware.org
mailing list for the glibc project.
[Bug nptl/14484] sem_timedwait always return -1 with errno 110 (ETIMEDOUT).
- From: "bugdal at aerifal dot cx" <sourceware-bugzilla at sourceware dot org>
- To: glibc-bugs at sources dot redhat dot com
- Date: Wed, 22 Aug 2012 01:08:22 +0000
- Subject: [Bug nptl/14484] sem_timedwait always return -1 with errno 110 (ETIMEDOUT).
- Auto-submitted: auto-generated
- References: <bug-14484-131@http.sourceware.org/bugzilla/>
http://sourceware.org/bugzilla/show_bug.cgi?id=14484
--- Comment #10 from Rich Felker <bugdal at aerifal dot cx> 2012-08-22 01:08:22 UTC ---
All your time calculation code is rather obfuscated and I haven't waded though
it yet, but I suspect you're just confusing microseconds and nanoseconds. The
fact that you're mixing interfaces that use timeval with ones that use timespec
does not help. I would switch to using POSIX timespec interfaces for everything
(timer_create for timers, clock_gettime for current time, etc.).
If it really is timing out early, this is probably due to the Linux kernel bug
for signal handlers interrupting syscalls with timeouts.
--
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.