clion break point is invalid for release

In CLion, breakpoints are used for debugging purposes and are typically not valid for release builds. This is because release builds are optimized and optimized code can make it difficult to accurately set breakpoints.

When you build your code in release mode, the compiler applies various optimizations to improve the performance of the code. These optimizations can change the order of instructions, eliminate unnecessary code, and inline function calls, among other things. As a result, the debug information generated in release builds may not accurately reflect the original source code, making breakpoints unreliable.

To debug a release build or find issues in production, it is recommended to use logging, assertions, or other error-handling techniques. Additionally, you can also consider enabling specific compiler flags or options to generate additional debug information in release builds, although this may have an impact on performance.

It is important to note that breakpoints are typically used during development and testing phases. Once your code is ready for release, it is usually compiled with optimizations enabled to improve its performance. Hence, breakpoints are generally not used in release builds