Interesting, this is a less common complaint than what I usually hear. It kind of makes sense if you run into this a lot (I don't in C++, but maybe it happens more in C?), but at the same time I'm wondering why can't you just e.g. use -fwrapv if you want to rely on integer wrapping in your release executable? It also doesn't sound like it's related to using a different compiler, since using the same compiler with a flag like -fwrapv or with optimizations disabled should also prevent UB from being exploited.

Sorry, I miscommunicated. I was not speaking about integer wrapping, I was speaking about undefined behaviour in a general sense.

Well if the compiler wraps signed numbers implicitly you have other issues.