DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2359 Version: 2.0-current So the problem is that if this *is* a bug, the usleep(1) (or however many milli/micro seconds) isn't really a valid fix. On a kernel level, threading works properly. Which means there's some form of (surprise surprise) bug in the 2.0 code, currently. I'm just trying to see if/where this bug exists, for now. All I've got currently is that it exists _somewhere_ inside the lock code :P The other problem is that this bug is being found in a prime checker - and since the distribution of primes isn't quite linear, we can't really use when "Max Prime:" is updated as a valid checking mechanism. ... and now that I've written all that, this bug definitely exists. I can only see it when running *two* threading demos at once though, so it's probably slightly dependent on cpu stress. Damnit. Oh well, I'll add this to the todo list, right after I fix the last two FileChooser STRs. Link: http://www.fltk.org/str.php?L2359 Version: 2.0-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
