Created an attachment (id=29610)
glx: Use initstate_r / random_r instead of corrupting global random number state
The hash table code actually needs some random numbers. Calling random may not be safe, regardless of the srandom issue, in multithreaded applications. Using initstate_r and random_r should fix these issues.
Created an attachment (id=29610)
glx: Use initstate_r / random_r instead of corrupting global random number state
The hash table code actually needs some random numbers. Calling random may not be safe, regardless of the srandom issue, in multithreaded applications. Using initstate_r and random_r should fix these issues.
Geir, could you test this patch?