@mattblaze since I'm not seeing it on your replies already, nobody can't take away your god-given right to segfault
@mattblaze Smashing the stack for God and country
—Phrack 49:14
You don't tell *me* I can't follow a null pointer. I'll follow any damn pointer I want!
Hold m'beer.
@mattblaze Curiously, in the 1980s, I wrote a simulator that would sometimes purposely overwrite the stack to provide multi-threading. This did not occur often enough for performance to be an issue, but it let me use the existing symbolic debuggers. That saved enough programmer time + debugging runs to pay for the inefficiency.
Needless to say, we don't have to resort to that today.
@mattblaze Land of the free(), home of the brave?
I heard that your candidate's memory model is really weak.