On Tue, Apr 20, 2021, at 09:45, Jeremy wrote: > Have a look at the arguments you can pass to "-fsanitize=" in gcc(1).
I am glad that you pointed that out to me--thank you. Does clang have comparable functionality? I gave up on using dvtm a while ago (now I use tmux which is good) because it would keep crashing. And I could not figure out how to debug the crashes or get specific information about the cause of the crashes. If I had known about these options then I would have compiled dvtm with them and maybe gave better bug reports. (Though I know C, I am not an expert in C.) Can someone point me to an article or blog post recommending which of these sanitize options would be recommended for general daily use? Are there any operating systems or (Linux) distributions that use these run-time checks by default, i.e. their binary packages are compiled with them? If enabling these run-time checks adds 5%, 10%, or even 25% to the run time or memory usage of a presumably already fast and small C binary executable, then it is worth it to me.
