Comment on CrowdStrike Isn't the Real Problem
SparrowRanjitScaur@lemmy.world 3 months agoMaybe I heard some bad information, but I thought the issue was caused by a null pointer exception in C/C++ code.
No one does, it’s not public yet, if ever. This is close enough.
The real problem was, among others, lack of testing, regardless of the programming language used. Blaming C++ is dumb af. Put a chimpanzee behing the wheel of a Ferrari and you’ll still run into… problems.
I’ll reiterate, if it was a null pointer exception (I honestly don’t know that it was, but every comment I’ve made is based on that assumption, so let’s go with it for now) then I absolutely can blame C++, and the code author, and the code reviewer, and QA. Many links in the chain failed here. But C++ is not a memory safe language, and while it’s had mass improvements in that area in the last two decades, there are languages that make better guarantees about memory safety.
but it very probably was not a memory error. Rust isn’t magic. It probably could not have prevented this bug anyway.
vrighter@discuss.tchncs.de 3 months ago
They said it was a “logic error”. so i think it was more likely some divide by zero or something like that