Re:Nvidia Security Team: “What if we just stopped using C?”
by wiseowise on Monday November 07, 2022 @12:58PM
(#33509480)
In C you leak memory because of all the land mines in the language. In Java/.Net you leak memory because you have flaw in your logic.
[ Parent
| on HN ]
Re:Nvidia Security Team: “What if we just stopped using C?”
by paulmd on Monday November 07, 2022 @02:38PM
(#33511179)
Circular references and other things that tend to leak memory on GC languages aren't a logic flaw in the sense of your business logic being wrong, though.
Re:Nvidia Security Team: “What if we just stopped using C?”
by scawf on Monday November 07, 2022 @03:52PM
(#33512264)
Circular reference does not leak memory if your using a proper GC
Re:Nvidia Security Team: “What if we just stopped using C?”
by donkeybeer on Monday November 07, 2022 @03:11PM
(#33511691)
Memory errors are always logic errors in C. Freeing something that was already freed or accessing a buffer out of bounds and so on are pure logic errors.
Re:Nvidia Security Team: “What if we just stopped using C?”
by pjmlp on Tuesday November 08, 2022 @03:34AM
(#33517137)
Plenty of logic errors in the last 50 years, CVE appeciates it.
Re:Nvidia Security Team: “What if we just stopped using C?”
by donkeybeer on Tuesday November 08, 2022 @04:54AM
(#33517598)
But that person was trying to say memory errors are some kind of special "magical" error, which is simply wrong. Memory errors are merely logical errors. There is nothing "special" or "mysterious" about them.