@spun_off The issue is that the object isn't big enough itself but it's contained within a buffer that's large enough so it's well-defined.
-
-
Replying to @CopperheadOS
@CopperheadSec @spun_off 1. How can you be sure that the buffer is large enough. Is the offset always 0? Then the function looks strange.1 reply 0 retweets 0 likes -
Replying to @ch3root
@CopperheadSec @spun_off If the offset is not 0 how do you know there is enough space left?1 reply 0 retweets 1 like -
Replying to @ch3root
@CopperheadSec @spun_off 2. I don't think you can as easily claim that this code is well-defined. By that logic "int a[4][5]; a[1][7]" is\4 replies 0 retweets 1 like -
Replying to @volatile_void
@ch3root we'll have a blog post up shortly about how we already find enough intentional UB that it's hard to convince people to fix.1 reply 0 retweets 1 like -
Replying to @volatile_void
@spun_off Interesting. The list of such cases will be useful. cc:
@hanno1 reply 0 retweets 0 likes -
Replying to @ch3root
@spun_off
@hanno 1. Perhaps the project "is implemented in GNU C, not in ISO C" ( https://sourceware.org/ml/libc-alpha/2014-05/msg00707.html … ). Who knows what GNU C is exactly1 reply 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.