Re: Gcc and undefined behavior

[Thorsten Glaser <tg@debian.org>]

Shachar Shemesh <shachar <at> debian.org> writes:

>     the changes there is a runtime check for undefined behavior. Just
>     compile with -fsanitize=undefined, and your program will crash with
>     log if it performs an operation that C/C++ considers to be
>     undefined.

This does not help. At all.

Consider:

• all possible codepaths

  ×

• all possible combinations of input/state data

Even “just” checking mksh would not work, for example.
Let alone OpenSSL.

Plus, crashing in a screensaver is bad :D

bye,
//mirabilos