Wow, the bug was a file of ALL NULLS. When executed/used it led to a null...

@mistersql

Wow, the bug was a file of ALL NULLS. When executed/used it led to a null pointer deref

Two layers of null unsafety.

youtu.be/pCxvyIx922A?t=188

Self-replies

Still, this is native code language with no null safety, no memory safety in general. It is entirely safe to assume that the whole application is seething with memory safety bugs and this one got thru. In 1950, people wrote native code with just 0's 1's and machismo. Today there is no excuse.

Fine, here is the comic so you don't need to reply: smbc-comics.com/comic/aaaah