Comment by tick_tock_tick

6 months ago

Here is a nice segfault in perfectly legal safe Rust https://play.rust-lang.org/?version=stable&mode=debug&editio...

I'd call it casting thought technically maybe it's not you might want to call it something else? You don't need transmute or leak. The issue is only 10 years old now https://github.com/rust-lang/rust/issues/25860

1 comment

tick_tock_tick

Reply
dwattttt  6 months ago

Yes, that's an existing soundness hole in the compiler. You won't accidentally code it up yourself though.

If the bar is "deliberately malicious code results in a segfault", get back to me when they fix

  memcpy(0x10000, 0x20000, 0x10);

EDIT: and even that's being charitable; the Rust issue is viewed as a compiler bug which should be fixed.