Heh, was gonna link that bug :) But there's an even simpler way: open /proc/self/mem in read-write mode. "Rust is safe" means something like, if you write code

Heh, was gonna link that bug :) But there's an even simpler way: open /proc/self/mem in read-write mode. "Rust is safe" means something like, if you write code to do a thing, it doesn't unintentionally lead to memory corruption. Opening /proc/self/mem is being fairly intentional about it. Colliding with a C function in another library could be unintentional, which is why I opened that, but most of the time (as with the blog post) it's fairly deliberate and obvious.