You know, double-free/invalid-free bugs could be trivially eliminated with an ABI having fat pointers.
-
-
Replying to @RichFelker
Also solves ABA problems, but you need wider atomic ops. We just end up doing it in-app :weep:
1 reply 0 retweets 0 likes -
Replying to @pkhuong @RichFelker
Solaris does something with the header to detect invalid frees at least.
1 reply 0 retweets 0 likes -
Replying to @pkhuong @RichFelker
Can reliably detect all invalid frees without probabilistic mitigations (i.e. leakable) by having out-of-line metadata.
2 replies 0 retweets 0 likes -
Detecting double-free after the allocation has gone back into circulation is the hard part although you can delay that.
1 reply 0 retweets 0 likes -
Not much that can be done about use-after-free once allocations have gone back into circulation after a delay though.
2 replies 0 retweets 0 likes -
Replying to @CopperheadOS @pkhuong
This thread is specifically about solving that problem, and it is (trivially) solvable with fat pointers.
1 reply 0 retweets 0 likes
You simply "never reuse addresses" by including a bunch of junk bits in the fat "address".
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.