From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12026 invoked by alias); 22 Aug 2012 05:21:48 -0000 Received: (qmail 12016 invoked by uid 22791); 22 Aug 2012 05:21:47 -0000 X-SWARE-Spam-Status: No, hits=-3.8 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00,KHOP_THREADED,TW_LR X-Spam-Check-By: sourceware.org Received: from localhost (HELO sourceware.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 22 Aug 2012 05:20:35 +0000 From: "tingw.liu at gmail dot com" To: glibc-bugs@sources.redhat.com Subject: [Bug nptl/14484] sem_timedwait always return -1 with errno 110 (ETIMEDOUT). Date: Wed, 22 Aug 2012 05:21:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: glibc X-Bugzilla-Component: nptl X-Bugzilla-Keywords: X-Bugzilla-Severity: critical X-Bugzilla-Who: tingw.liu at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at sourceware dot org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://sourceware.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" MIME-Version: 1.0 Mailing-List: contact glibc-bugs-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: glibc-bugs-owner@sourceware.org X-SW-Source: 2012-08/txt/msg00140.txt.bz2 http://sourceware.org/bugzilla/show_bug.cgi?id=14484 --- Comment #11 from tingweiliu 2012-08-22 05:20:34 UTC --- (In reply to comment #10) > 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. OK... Can you tell me why the output is different with the same system.(Linux 2.6.32) gcc sem_timedwait.c -lrt -o sem_timedwait One is like: #./sem_timedwait sem_timedwait ret=-1 failed.errno=110 Real timeout=4us sem_timedwait ret=-1 failed.errno=110 Real timeout=4us sem_timedwait ret=-1 failed.errno=110 Real timeout=4us sem_timedwait ret=-1 failed.errno=110 Real timeout=4us Another is like: #./sem_timedwait sem_timedwait ret=-1 failed.errno=4 Real timeout=3948us sem_timedwait ret=-1 failed.errno=4 Real timeout=3929us sem_timedwait ret=-1 failed.errno=4 Real timeout=3958us sem_timedwait ret=-1 failed.errno=4 Real timeout=4149us sem_timedwait ret=-1 failed.errno=4 Real timeout=3967us sem_timedwait ret=-1 failed.errno=4 Real timeout=3818us -- 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.