Hi,
Firefox uses a technique they call frame poisoning to mitigate
dangling pointer bugs. It reserves a poison area at a fixed location
in the address space (and tries other places if that can't be done)
and makes dangling pointers point there so that the application ends
up crashing instead of
On Sun, Oct 31, 2010 at 10:38:06AM +0100, Philipp Kern wrote:
Mike,
am Sun, Oct 31, 2010 at 08:54:10AM +0100 hast du folgendes geschrieben:
Firefox uses a technique they call frame poisoning to mitigate
dangling pointer bugs. It reserves a poison area at a fixed location
in the address
On Sun, Oct 31, 2010 at 10:51:36AM +0100, Mike Hommey wrote:
During the build, this is what happens:
INFO | negative control allocated at 0x40028000
INFO | positive control allocated at 0x4002a000
INFO | poison area assumed at 0xf0dea000 (preferred addr)
TEST-PASS | reading negative control
3 matches
Mail list logo