News for hackers. Stuff that matters.

A comment on A Guide to Undefined Behavior in C and C++ (2010). Parent comment

Re:A Guide to Undefined Behavior in C and C++ (2010) by the_why_of_y on Sunday November 04, 2018 @07:26AM (#18375544)
That presumes that your testing process will find the input that actually triggers the UB in your program before the release.

The CVE history of the major browser vendors indicate that this is currently an unsolved problem for their large C++ applications.

[ Parent | on HN ]
Re:A Guide to Undefined Behavior in C and C++ (2010) by flohofwoe on Sunday November 04, 2018 @08:07AM (#18375673)
Of course, and that's exactly where Rust makes sense. Few pieces of software are as safety-critical and complex as a browser though, that's why I'm not a fan of the general "UB scaremongering" ;)
[ Parent | on HN ]