Vi • 
The crowdstrike bug is showing me how many people on linkedin with "C++ expert" in their bio don't understand what basic null pointer dereferences look like in dumps
Diane Bruce@vi *sigh*
Scruffy looking packet herder@vi @DianeBruce I a network engineer who writes some super bad shell and python form time to time knows better, FFS
@sng @vi I've done embedded debug which can be... fun FCVO. Nothing quite like a pointer that... oh wait that's an ASCII string? N.B. Some of the earliest ports of UNIX allowed a deref of 0 (They had a 0 conveniently written there so some could check for *s getting both NULL pointer and nul char at the same time) without a SIGEGV (strictly speaking it's a Undefined behaviour. esp. so on some of the real time machines I worked on. It wouldn't core.) There was a pile of userland unix code that had to be fixed...This is from... a long time ago and I cannot find a modern reference to this. :-(
Whoever this C++ coder is they are a clueless newbie.
Whoever this C++ coder is they are a clueless newbie.
Todd C. Miller@DianeBruce @sng @vi That was from the "all the world's a VAX" days. https://www.catb.org/jargon/html/V/vaxocentrism.html