undefined | Better HN

0 pointsarray_key_first1mo ago0 comments

You cannot tell if code is actually reachable if it depends on runtime input.

Those really evil bugs are the ones that exist in code paths that only trigger 0.001% of the time.

Often, the code path is not triggerable at all with regular input. But with malicious input, it is, so you can only find it through fuzzing or human analysis.

0 comments

userbinator1mo ago

You cannot tell if code is actually reachable if it depends on runtime input.

That is precisely what a static analyser can determine. E.g. if you are reading a 4-byte length from a file, and using that to allocate memory which involves adding that length to some other constant, it will assume (unless told otherwise) that the length can be all 4G values and complain about the range of values which will overflow.

j / k navigate · click thread line to collapse

0 comments

userbinator1mo ago

You cannot tell if code is actually reachable if it depends on runtime input.

j / k navigate · click thread line to collapse