@CopperheadSec @ch3root Integrrs don't have "memory" of where they came from. Imagine printf, user types it back, scanf.
@CopperheadSec @ch3root But its not. The rules about integer to pointer conversions and uintptr_t are not respected by this.
-
-
@RichFelker@ch3root The logic is that valid code constructing a pointer this way must derive it from an existing pointer in practice. -
@RichFelker@ch3root It might not be true though... one example is the incorrect __attribute__((malloc)) on strdup in glibc. -
@RichFelker@ch3root It tells the compiler that the returned data (not just the outer pointer) cannot alias an existing pointer. -
@CopperheadSec@ch3root Ouch, that sounds very bad. -
@RichFelker@ch3root Yeah, look at the description in https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#Common-Function-Attributes …. The glibc usage on strdup appears to be completely wrong. -
@CopperheadSec@ch3root Is there an open bug report for this? -
@RichFelker@CopperheadSec A bug report where? gcc folks say that such things are done according with DR 260. -
@RichFelker@CopperheadSec And I don't see anything else except DR 260 that will prohibit my original example. - 1 more reply
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.