Comment by saagarjha 3 years ago Note that UBSan is a dynamic analysis tool. 4 comments saagarjha Reply pjmlp 3 years ago Thanks for the correction, one should use those as well on debug builds for integration tests. saagarjha 3 years ago Agreed :) eru 3 years ago Indeed. But still a good idea to run at least your test-suite with it. And also with address sanitizer and clang's memory sanitizer, etc. Whatever you can find. astrange 3 years ago The static analysis is you compile with it and see if there's any trap instructions emitted by the compiler.(The answer is: yes.)
pjmlp 3 years ago Thanks for the correction, one should use those as well on debug builds for integration tests. saagarjha 3 years ago Agreed :)
eru 3 years ago Indeed. But still a good idea to run at least your test-suite with it. And also with address sanitizer and clang's memory sanitizer, etc. Whatever you can find.
astrange 3 years ago The static analysis is you compile with it and see if there's any trap instructions emitted by the compiler.(The answer is: yes.)
Thanks for the correction, one should use those as well on debug builds for integration tests.
Agreed :)
Indeed. But still a good idea to run at least your test-suite with it. And also with address sanitizer and clang's memory sanitizer, etc. Whatever you can find.
The static analysis is you compile with it and see if there's any trap instructions emitted by the compiler.
(The answer is: yes.)