3 ms·
Frankly, 0xdeadbeef is a rather bad value for a pointer poison: It doesn't have enough leading zeros to be caught in unmapped area used to catch null pointer ac
by danvet 16y ago
Frankly, 0xdeadbeef is a rather bad value for a pointer poison: It doesn't have enough leading zeros to be caught in unmapped area used to catch null pointer access (it has a high change of being a valid kernel address on linux if you have about 700mb of ram). And there are not enough zeros at the end to still recognize it if the access is to a offset within the array/structure (as it usually happens).
Not catching the usage of a poisoned pointer on first access creates enormous amounts of fun - normally preventing any meaningful analysis of dumps.
- demallien 16y agoAgreed - not only do I find "DEAD BEEF" as a rather gross concept, but there are technical flaws, as you point out. I personally prefer the simple, form-matches-function 0x0000DEAD. Yup, that pointer's dead baby!