Thread: Checking for runtime violations

Hey. Is there a way I could enable runtime checking using some compilation flags for things like out_of_bounds access or signed integer overflow. Usually when I have such problems, my executable simply crashes. I've seen people (on streams) get messages like "Access Violation on line XX..." or something when there happens to be such errors but I haven't figured out how to enable this myself.

For out of bounds checking you would compile without defining NDEBUG and enable options like checked iterators, as well as placing your own pre-condition/post-condition assertions.

I'm not sure I understand completely. I realised I was compiling without -D_GLIBCXX_DEBUG, after which, I get messages like (which is what I wanted):

Code:

c:\programming\mingw\mingw 9.2.0\include\c++\9.2.0\debug\vector:427:
In function:
    std::__debug::vector<_Tp, _Allocator>::reference
    std::__debug::vector<_Tp,
    _Allocator>::operator[](std::__debug::vector<_Tp,
    _Allocator>::size_type) [with _Tp = int; _Allocator =
    std::allocator<int>; std::__debug::vector<_Tp, _Allocator>::reference =
    int&; std::__debug::vector<_Tp, _Allocator>::size_type = long long
    unsigned int]


Error: attempt to subscript container with out-of-bounds index 10000, but
container only holds 5 elements.


Objects involved in the operation:
    sequence "this" @ 0x000000000023FD90 {
      type = std::__debug::vector<int, std::allocator<int> >;
    }


This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.

Upon further reading, I came across stuff like -fsanitize=address and -fsanitize=undefined. I'm not sure I understand how to make it work yet but could you give a brief description on what it's supposed to do?