| Follow @JnyJny
Austin, Tx-ish
Erik O'Shaughnessy is an opinionated but friendly UNIX system programmer living the good life in Texas. Over the last twenty years (or more!) he has worked for IBM, Sun Microsystems, Oracle, and most recently Intel doing computer system performance related work. He is; a mechanical keyboard aficionado, a gamer, a father, a husband, voracious reader, student of Okinawian karate, and seriously grouchy in the morning before coffee.
Authored Comments
Welcome to the unbounded joy that is C! I considered briefly not using uint32_t (or a cognate) in my code, but this article was originally titled "How To Write a C Main Function Like Me" so I wrote it the way I would normally write it. When I was writing C regularly, it was nearly always in support of a particular software/hardware combination that was reasonably "static" and only changed for major/minor OS updates or forklift hardware upgrades. Today's programming environments are much more fluid and you have to decide how much you want to "forage" from the environment and how much you are willing to re-implement to avoid the problems like the one you encountered.
Ok, I'm not even going to try to lie. I went back and checked my source notes and sure enough, it's SYSSEGV there too. It just goes to show that editing is hard when there isn't a compiler keeping you honest. Thanks for the extra editing, your check is in the mail! ;)