On Fri, 17 Jan 2003 [EMAIL PROTECTED] wrote: > Yes, silly me. Just saving the data sent in the current connection to > a file should help a lot, I did not bother about it because at every > crash I was able to understand what was wrong by just inspecting the > server state and the stack (sometimes it overwritten due to buffer > overflows, but some investigation like casting stack addresses to a > struct pointer, etc, allowed understanding from where it was overwritten). > But besides timing differences, it is also possible that an earlier > connection do not crash the server, but changes the server internal state > causing a crash in a later connection. Saving a few hours of almost > continuous /dev/urandom will needs a large amount of storage :-) > > This sounds like an interesting project for a testing tool/environment.
Use a less random number generator, such as rand(). Provided you store the seep used when calling srand, the sequence is repeatable. It may not be as random, but it is likely to flush out most bugs eventually. -- Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
