Bug in time.c (was Time.times problems) 
Author Message
 Bug in time.c (was Time.times problems)

Hi,

In message "[ruby-talk:15387] Re: Bug in time.c (was Time.times problems)"

|That's strange. On both my boxes, the man page doesn't mention an
|error for either function. However, if the buffer address is bad, they
|do indeed return EFAULT. So I retract the bug in Ruby, and claim a bug
|in my man pages :)

I'm confusing why starange behavior had happened for Guy's program.
In Ruby's source code, no bad address is given to times(2), so that if
EFAULT is the only error for times(2), I can just ignore error code.

                                                        matz.



Wed, 05 Nov 2003 12:08:42 GMT  
 
 [ 1 post ] 

 Relevant Pages 

1. time and scheduling (was: bug report: [ #447945 ] time.time() is not non-decreasing)

2. time zones, daylight saving time, and universal time

3. bug report: [ #447945 ] time.time() is not non-decreasing

4. bug report: [ #447945 ] time.time() is not non-decreasing

5. Run-time & Design-time window size problem

6. Help!: problem with fast timing for real-time application on PC

7. Time.times problems in libc5; getrusage request

8. Help!: problem with fast timing for real-time application on PC

9. Manugistics run-time [was: STSC run-time]

10. GMT time vs. local time

11. Comparing system time and log file time

12. converting time in a string to a time field

 

 
Powered by phpBB® Forum Software