Open Eebo78 opened 5 years ago
Interesting behaviour... I guess VS2017 is optimizing some stuff which it should not do.
There are two ways to find out where the issue occurs:
Maybe you can generate somehow debug symbols together with the MinSizeRel build to be able to see where the exception happens. Maybe https://docs.microsoft.com/en-us/cpp/build/reference/how-to-debug-a-release-build?view=vs-2017
If you can not generate debug symbols, you can use printf or logging, step by step adding it to the code to find the last output before it crashes. Maybe setting the log level to TRACE also helps to find the line
Description
Building the examples using the MinSizeRel build configuration in Visual Studio 2017 the tutorial_server_firststeps.exe crashes. Running the sample from VS throws an access violation exception. Debug and Release configurations works fine. Same issue on win32 and x64.
Background Information / Reproduction Steps
Checklist
Please provide the following information:
UA_LOGLEVEL
set as low as necessary) attached