On 5/2/06, Ed White <[EMAIL PROTECTED]> wrote:
- When you free an object that is >= 1 page in size, it is actually
returned to the system. Attempting to read or write to it after
you free is no longer acceptable. That memory is unmapped. You get
a SIGSEGV.
- For a decade and a bit, we have been fixing software for buffer overflows.
Now we are finding a lot of software that reads before the start of the
buffer, or reads too far off the end of the buffer. You get a SIGSEGV.
But it seems that this feature was disabled just before shipping 3.8 because
too many ports were instable. 3.9 should come with it.
how does it seem this feature was disabled? look at cvs log. nothing
was disabled.
