Bug 1088455 - strace does not know about CLOCK_BOOTTIME
Summary: strace does not know about CLOCK_BOOTTIME
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: strace
Version: 20
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Dmitry V. Levin
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-04-16 16:20 UTC by john.haxby@oracle.com
Modified: 2014-08-19 14:22 UTC (History)
3 users (show)

Fixed In Version: 4.9-1
Clone Of:
Environment:
Last Closed: 2014-08-19 14:22:43 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
proposed patch (385 bytes, patch)
2014-04-16 16:21 UTC, john.haxby@oracle.com
no flags Details | Diff

Description john.haxby@oracle.com 2014-04-16 16:20:07 UTC
Description of problem:

Given this tiny program:

        #include <time.h>

        int main () {
                struct timespec t;
                clock_gettime(CLOCK_BOOTTIME, &t);
                return 0;
        }

strace prints "0x7 /* CLOCK_??? */" instead of CLOCK_BOOTTIME

Version-Release number of selected component (if applicable):
   strace-4.8-1.fc20.x86_64


How reproducible: every time


Steps to Reproduce:
1. Compile the tiny program above
2. strace -e clock_gettime ./a.out
3. Observe clock_gettime system call

Actual results:

   clock_gettime(0x7 /* CLOCK_??? */, {17973, 83774407}) = 0


Expected results:

   clock_gettime(CLOCK_BOOTTIME, {17973, 83774407}) = 0

Additional info:

I've attached a proposed patch, but strace itself doesn't build with the current kernel and headers (some different problem I've not looked into).  The patch itself is trivial though.

Comment 1 john.haxby@oracle.com 2014-04-16 16:21:06 UTC
Created attachment 886932 [details]
proposed patch


Note You need to log in before you can comment on or make changes to this bug.