Sounds like you’re saying that this is another UB that is trivial to fix by just specifying that variables get zero-initialized.
-
-
Replying to @johnregehr @samth
OOB and UAF means you write to some other object or trap. Seems easy to specify to me.
1 reply 0 retweets 0 likes -
Replying to @johnregehr @samth
Doing random stuff and writing to a random object are different statements. The latter does not permit demons in the nose.
1 reply 0 retweets 0 likes -
Replying to @filpizlo @johnregehr
It has to be allowed to write to - the stack - anywhere in the heap - out of bounds triggering a segfault - whatever embedded devices do - probably other stuff too
3 replies 0 retweets 1 like -
Let’s go even further: UB has to be allowed to write to the current instruction pointer if W^X is not enabled. So literally anything can happen. :)
4 replies 2 retweets 3 likes
(Assuming that the CPU is not constrained in the things it can do.)
6:35 PM - 31 May 2018
from Civic Center, San Francisco
0 replies
0 retweets
0 likes
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.