Seriously. Sometimes, C does things that make absolutely no sense. Dereferencing a NULL pointer is one thing. CHECKING if something is NULL causing crashes is... janky to say the last. Nearest I can figure, if there's a full moon on Pi day (3/14 at 1:59 AM) and the planets are aligned just right, the gremlins come out to play.

These logic-defying bugs are hidden behind the most obscenely cryptic pile of mumbo-McJumbo I've ever heard. "Segmentation fault (core dumped)." Okay, what's segmented and/or faulty? My system has 4 cores. Why you dumping on my cores, dude? It's like the system was only ever intended to be used by the people who built it. I tried looking it up on YouTube, and got a lot of people whose English was practically incomprehensible (maybe I should try typing my search keywords in Spanish? lol I speak Spanish so maybe) and all kinds of way-over-my-head stuff about looking at the underlying Assembly (and the only Assembly language I know is 6502) and all kinds of... just... nonsense... lol sorry, one of those exasperatingly long nights. Can't sleep, can't think straight, but would love to unlock the buried treasure that must be behind that fateful message.

Does anyone know of a really good, clear-cut, straightforward tutorial, or collection of tutorials, for cracking the cipher behind this thing? Right now the error may as well be "Deep Magic from the Dawn of Time" (lol a nod to my fellow Narnia fans before I make like my program and crash).