Re: [reSIProcate] Exception encountered when using reSIProcate in a multi-threaded program
Alan,
Can you explain the situation when random number
generator is initialized repeatedly? From the source
code pasted below, it is initialized only once.
int
Random::getRandom()
{
if (!mIsInitialized)
{
initialize();
}
...
kaiduan
--- Alan Hawrylyshen <alan@xxxxxxxxxx> wrote:
>
> 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
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
>
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com