What is the recommended way to make sure that every access or write to array (allocated on stack) is actually valid (i.e. not provoking undefined behaviour) ? What if use clang on Linux with the options -fsanitize=addressand -fsanitize=undefined? It is also available in gcc: http://gcc.gnu.org/gcc-4.8/changes.html. clang with the option -fsanitize=undefined This is an example: #include … Read more
I suggest setting set(CMAKE_EXPORT_COMPILE_COMMANDS ON) in the CMakeList.txt
If realloc() fails it returns NULL. So if you do (and assuming realloc() would fail) result = realloc(result, …); result will be assigned NULL and what it pointed to is not free()ed and the address to be free()ed is lost. To fix this do: { void * tmp = realloc(result, …); if (NULL == tmp) … Read more
I used this code from (originally from here): #include <windows.h> void usleep(__int64 usec) { HANDLE timer; LARGE_INTEGER ft; ft.QuadPart = -(10*usec); // Convert to 100 nanosecond interval, negative value indicates relative time timer = CreateWaitableTimer(NULL, TRUE, NULL); SetWaitableTimer(timer, &ft, 0, NULL, NULL, 0); WaitForSingleObject(timer, INFINITE); CloseHandle(timer); } Note that SetWaitableTimer() uses “100 nanosecond intervals … … Read more