cvs commit: src/games/random random.c
Greg 'groggy' Lehey
grog at FreeBSD.org
Thu Jun 23 01:06:40 GMT 2005
On Wednesday, 22 June 2005 at 14:45:09 -1000, juli mallett wrote:
> * Greg 'groggy' Lehey <grog at FreeBSD.org> [ Date: 2005-06-22 ]
> [ w.r.t. Re: cvs commit: src/games/random random.c ]
>> On Wednesday, 22 June 2005 at 14:31:48 -1000, juli mallett wrote:
>>> * Greg 'groggy' Lehey <grog at FreeBSD.org> [ Date: 2005-06-22 ]
>>> [ w.r.t. Re: cvs commit: src/games/random random.c ]
>>>> On Wednesday, 22 June 2005 at 15:24:00 +0000, John Baldwin wrote:
>>>>> jhb 2005-06-22 15:24:00 UTC
>>>>> Correct an error in the previous revision. RAND_MAX is the maximum value
>>>>> for rand(3), not random(3). random(3) is defined to return values between
>>>>> 0 and 2^31-1, so add a local RANDOM_MAX constant to this file that is
>>>>> defined as 2^31-1 and use that in place of RAND_MAX.
>>>> How much effect did this bug have on the results of random(3)?
>>> How would a bug in random(6) bounds checking affect the results
>>> of random(3)?
>> You tell me. The commit message only refers to random(3).
> The commit was to random(6) and the commit message was in reference
> to the use of random(3) by random(6). I suspect one of us is very
> confused and/or not reading the emails we reply to.
Your confusion appears to stem from the expectation that the commit
log message need not describe the issue adequately.
The virus contained in this message was not detected.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 187 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/cvs-all/attachments/20050623/14fa9fdb/attachment.bin
More information about the cvs-all