Hey guys, I am developing a commercial fork of Blender that is adding a new icon based interface to Blender 2.8
My problem is that I experience a crash in my release build (both make full [build without Cuda] and make release [built with Cuda] ) that I do not experience with the debug build. I am not looking for a ready made solution from you, cause I like to figure out things myself. But still I have to admit being very inexperienced with C and more so with Blender source I was wondering how you deal with bugs that appear in release builds but not in the debug builds.
I just discovered the problem so I have not the time to really find a solution , my course of action is to insert breakpoints in my code for the release build until I find when exactly Blender crashes. I am using VS 2017 and I dont make use of the command line.
The only things I know so far is that its a memory access violation bug or so it reports in the command line.
c:\ephestos\ephestos001\bin\Release>blender.exe
Read prefs: C:\Users\kilon\AppData\Roaming\Blender Foundation\Blender\2.80\config\userpref.blend
found bundled python: c:\ephestos\ephestos001\bin\Release\2.80\python
Traceback (most recent call last):
File "c:\ephestos\ephestos001\bin\Release\2.80\scripts\modules\addon_utils.py", line 383, in enable
raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")
Exception: Add-on 'io_curve_svg' has not been upgraded to 2.8, ignoring
Traceback (most recent call last):
File "c:\ephestos\ephestos001\bin\Release\2.80\scripts\modules\addon_utils.py", line 383, in enable
raise Exception(f"Add-on '{module_name:s}' has not been upgraded to 2.8, ignoring")
Exception: Add-on 'pie_menus_official' has not been upgraded to 2.8, ignoring
Error : EXCEPTION_ACCESS_VIOLATION
Address : 0x00007FF776DC3F43
Module : c:\ephestos\ephestos001\bin\Release\blender.exe
Are there tools and techniques to help me identify such tricky bugs ?
Any not so obvious debug tools for Blender I can use to assist me ? For example I have seen that Blender employs its own printf functions to print debug information.
Any tip and tricks, experiences or general advice is more than welcomed. Thanks