Any time I am calling the senselClose() function, my app crashes.
If I run the debugging, I get this message: “Exception non gérée à 0x00007FFB6C968353 (ntdll.dll) dans Max.exe : 0xC0000374: Un segment de mémoire a été endommagé (paramètres : 0x00007FFB6C9BF6B0).”.
Translation: Unhandeld exception at à 0x00007FFB6C968353 (ntdll.dll) in Max.exe: 0xC0000374: A fragment of memory has been damaged (parameters: 0x00007FFB6C9BF6B0).
Some suggestions from a fellow developer, if you haven’t already tried them.
There are memory-heap validation functions that can be called, prior to calling senselClose() and throughout the code, which might help detect if and where memory is being overwritten/damaged. E.g. in Visual Studio one can use ASSERT(_CrtCheckMemory()); This command checks the heap at (and only at) the spot it is inserted. There are other related memory debugging mechanisms, as well.
Comment-out the calls to senselClose(). Does it then crash elsewhere?
that all existing code will still work, but the compiler will then warn about the kind of error that amundsen ran into. I tested this and it seems to work.
If the main issue is you do not know that how to access the missing ntdll.dll files, so learn from here how to fix the error and keep your computer secure also.