Re: clock(3) non-functional?

[Svante Signell <svante.signell@gmail.com>]

On Sun, 2014-06-29 at 22:56 +0200, Samuel Thibault wrote:
> Hello,
> 
> Svante Signell, le Sun 29 Jun 2014 16:35:42 +0200, a écrit :
> > Looking at libsamplerate test problems, I found that clock(3) used
> > there is not reliable. Strange results are obtained on too Linux with a
> > simple test program.
> 
> What do you mean by "strange"? The output I get
> 
> $ ./test
> start = 3870
> end = 3910
> cpu_time_used = 0.000040

I get:
gcc -g -Wall test_clock.c
./a.out
start = 0
end = 0
cpu_time_used = 0.000000

ldd ./a.out
        libc.so.0.3 => /lib/i386-gnu/libc.so.0.3 (0x0103f000)
        /lib/ld.so => /lib/ld.so.1 (0x00001000)
        libmachuser.so.1 => /lib/i386-gnu/libmachuser.so.1 (0x011ff000)
        libhurduser.so.0.3 => /lib/i386-gnu/libhurduser.so.0.3
(0x01217000)