On Tue, 17 Jul 2007, Davi Arnaut wrote:
> Michael Kerrisk wrote:
> >
> > Hi Davide,
> >
> > While writing a test program to incorporate into the timerfd.2 man page, I
> > think I've found a bug. It looks like only the least significant byte of
> > ticks is being returned from read(2), even
Michael Kerrisk wrote:
>
> Hi Davide,
>
> While writing a test program to incorporate into the timerfd.2 man page, I
> think I've found a bug. It looks like only the least significant byte of
> ticks is being returned from read(2), even though I am providing a 4 byte
> buffer.
>
> The test
Hi Davide,
While writing a test program to incorporate into the timerfd.2 man page, I
think I've found a bug. It looks like only the least significant byte of
ticks is being returned from read(2), even though I am providing a 4 byte
buffer.
The test program takes 3 command line arguments:
1)
Hi Davide,
While writing a test program to incorporate into the timerfd.2 man page, I
think I've found a bug. It looks like only the least significant byte of
ticks is being returned from read(2), even though I am providing a 4 byte
buffer.
The test program takes 3 command line arguments:
1)
Michael Kerrisk wrote:
Hi Davide,
While writing a test program to incorporate into the timerfd.2 man page, I
think I've found a bug. It looks like only the least significant byte of
ticks is being returned from read(2), even though I am providing a 4 byte
buffer.
The test program
On Tue, 17 Jul 2007, Davi Arnaut wrote:
Michael Kerrisk wrote:
Hi Davide,
While writing a test program to incorporate into the timerfd.2 man page, I
think I've found a bug. It looks like only the least significant byte of
ticks is being returned from read(2), even though I am
6 matches
Mail list logo
