this post was submitted on 21 Jul 2024
191 points (76.5% liked)
Technology
59374 readers
7409 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related content.
- Be excellent to each another!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, to ask if your bot can be added please contact us.
- Check for duplicates before posting, duplicates may be removed
Approved Bots
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
C++ is the problem. C++ is an unsafe language that should definitely not be used for kernel space code in 2024.
the virus definition is not written in c++. And even then, the problem was that the file was full of zeros.
Maybe I heard some bad information, but I thought the issue was caused by a null pointer exception in C/C++ code. If you have a link to a technical analysis of the issue I would be interested to read it.
They said it was a "logic error". so i think it was more likely some divide by zero or something like that
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.
C++ is not a memory safe language, and while it's had massive 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.