Segmentation fault

Segmentation fault

Attached: p19cpcvtrh7sm1hqqjas172v11k73.jpg (590x290, 14K)

Attention gentlemen, there's something I would like to say.
*ahem*
fn main() {
unsafe { *std::ptr::null_mut::() = 0; }
}

Attached: pepe mic.jpg (511x671, 41K)

>running code under an OS

Attached: gigachad.jpg (633x711, 23K)

gdb, valgrind

it means you fucked up so bad it wont even help you debug it, cause you dont deserve

>tfw even crashing your program is so verbose and ugly in rust

Attached: 1515382257000.jpg (275x277, 54K)

[spoiler]apt-get install valgrind[/spoiler]

wouldn't it be funny if the compiler did the static analysis itself haha

what percentage of libs are not written in C?

They all have to be in C, how else are we supposed to pwn the libs?

slow
-fsanitize=address -fsanitize=undefined and learn the clang static analyzer

Now this is an abstract kind of cancer.

main:
call unsafeFunction
int 33h
unsafeFunction:
xor rsi, rsi
mov rdi, 0ffffffffffffffffh
mov rcx, rdi
rep stosq
ret

Attached: lCQ5mPg.png (380x380, 119K)

Learn to code properly.

Sanity check fails? abort();

>Error: the "impossible happened.

Y'all are just mad C implements generics without the need for templates.

Except it doesn't. void * is a lot less safe, and more importantly, it uses more indirection, which harms performance.
This is the main reason why std::sort is noticeably faster than qsort.

It's rather have my compiler spend 2 seconds analyzing code instead of fuzzing everything and running it through valgrind on every release.

>detailed type information makes code faster
Shhh, you are gonna confuse the typelets.

Blah blah unsafe. A cliche criticism. Generics in C are not duplicated via templates. There's just one copy of your code that works across all implementations.

oohhhhh this nigga dab on

> boost error
How do you even figure out what went wrong? There has to be a boost error interpreter