On Tue, 19 Mar 2002, Matthew Dillon wrote: > Yes, this has been fixed. Python was using MAP_ANON|MAP_NOSYNC > mmap()'s and this resulted in the possibility of msync() encountering > an optimized vm_map_entry that did not yet have a VM object associated > with it, causing a panic. > > Both -stable and -current have been fixed to handle the case. > -current was fixed on March 7th, and -stable on March 8th.
Does that mean that RELENG_4_5 has that patched also? -- Winfried mail: [EMAIL PROTECTED] http://violent.dream.vg JS500-RIPE Warning: Never underestimate the power of stupid people in large numbers. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-stable" in the body of the message
