You know, double-free/invalid-free bugs could be trivially eliminated with an ABI having fat pointers.
-
-
Non-malloc pointers have arbitrary (e.g. all zero bits). Now free can trap if the id in the fat pointer doesn't match the pointed-to block.
-
cool idea. would it be possible (or worthwhile) to cram a 16-bit ID into the unused high-order bits on x86-64?
-
I don't think so. It's insufficient to protect against intentional attacks and mandates an ABI change anyway.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.