Oh snap!

>>59092831
Panic

File: 1482170812547.jpg (114KB, 350x420px) Image search: [Google]

114KB, 350x420px

>>59092831
Use a better language like Java.
>captcha: calle calle

>>59092831
It's okay, I have an exception.

File: 1485826266425.gif (912KB, 240x176px) Image search: [Google]

912KB, 240x176px

>>59092831
Fire all pajeets responsible

File: exterminate.jpg (61KB, 666x632px) Image search: [Google]

61KB, 666x632px

>>59092831
Put my best PR people on it and scapegoat third parties.

>>59092831
I fix the security loophole with my command line via POSIX/CMD to prevent further infection in the mainframe.

Use a better language like Rust.

>>59092831
Rewrite the parser using parser combinators instead of that retarded shit cf-html going on now.

>>59092831
Unplug the monitor so i can't get hacked

Turn it off and go to my real job in academia

>>59092943
>Java
>for a string parser that needs to run fast as fuck in limited ram

How about hiring competent devs?

install openbsd

Rewrite the code in Holy C

wasn't a null pointer deref, it was a buffer overrun.

https://blog.cloudflare.com/incident-report-on-memory-leak-caused-by-cloudflare-parser-bug/

kys my'selvfes

Give out free t-shirts

How could a null pointer compromise anything? Just use a try-catch.

A non-null pointer that's SUPPOSED to be null, on the other hand...

Use a better language like D.

use something like bison, antlr or literally any proper grammar spec language instead of writing the shitty parser in C myself.

not use a shitty cdn

>>59092831
>hire pajeets
>susprised when this happens

But then again nobody will give a shit and forgive cloudfare