[reSIProcate] Exception encountered when using reSIProcate in a multi-threaded program

[Alan Hawrylyshen]

On Jul 18, 2005, at 17.38, Fischl jason wrote:

>
> You may also need to put debug in Random::getRandomHex. Possibly we're
> getting nailed on some win32 thread safety issue with getRandom. Focus
> your effort there.
>


It just dawned on me that this behavior can arise when (if) the  
random number generator is initialized repeatedly.
If the seed it timebased and your call resolution is smaller than the  
clock resolution, you will get duplicates.

Alan