Dag-Erling Smorgrav wrote: > Plus, your program doesn't even do what you think it does (because a) > it has at least one significant bug and b) malloc() doesn't behave the > way you think it does). And even if it did, the /dev/random stuff is > pointless, you can achieve the same effect by setting every byte you > allocate (possibly even just the first byte of every chunk) to 0. So now the question becomes "what is he testing that is resulting in 4.3 locking up?". Your suggested replacement test might be fun to run, but I think it wouldn't lock up 4.3... -- Terry To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
- Re: pgm to kill 4.3 via vm Dag-Erling Smorgrav
- Re: pgm to kill 4.3 via vm Terry Lambert
- Re: pgm to kill 4.3 via vm Dag-Erling Smorgrav
- Re: pgm to kill 4.3 via vm Matt Dillon
- Re: pgm to kill 4.3 via vm Sheldon Hearn
- Re: pgm to kill 4.3 via vm Dag-Erling Smorgrav
- Re: pgm to kill 4.3 via vm Dennis Glatting
- Re: pgm to kill 4.3 via vm Dag-Erling Smorgrav
- Re: pgm to kill 4.3 via vm Szilveszter Adam
- Re: pgm to kill 4.3 via vm Daniel C. Sobral
- Re: pgm to kill 4.3 via vm Terry Lambert
- Re: pgm to kill 4.3 via vm Dag-Erling Smorgrav
- Re: pgm to kill 4.3 via vm Dima Dorfman
- Re: pgm to kill 4.3 via vm John Baldwin
- Re: pgm to kill 4.3 via vm Robert Watson
- Re: pgm to kill 4.3 via vm John Baldwin
- Re: pgm to kill 4.3 via vm Robert Watson
- Re: pgm to kill 4.3 via vm Dima Dorfman
- Re: pgm to kill 4.3 via vm John Baldwin
- Re: pgm to kill 4.3 via vm Garrett Wollman
- Re: pgm to kill 4.3 via vm Robert Watson