@aryeramaty Sorry I could not find the time to test you very diff to debug (I’m working on my own branch, it takes a lot of time to switch to a vanilla Blender to test this). Thanks a lot for your feedback. You’re not the first to report that a clear list of modified code would be easier to follow, so I’ll improve this (as well as the list of modified files). I just don’t want the tutorial to become a series of copy paste to execute blindly, because this would not be as helpful and would be less robust to changes in the code base. ANyways, I can do better and I will!
@aryeramaty @Hermenator Use the debugger to troubleshot the issue. When running your custom Blender with a debugger (gdb if you’re on linux, Visual Studio in Debug mode on Windows, or whatever other solution), than a segmentation fault should trigger the debugger and let you explore at the very moment of the crash the line of code that was being executed, the value of variables in the scope, the stack of function calls that lead to this line, etc. It’s close to impossible to debug this kind of runtime error without using a debugger. 
@Kanzari-Haithem I actually bumped into this issues multiple times on other machines than mine, and I don’t know what causes this and it is really annoying, let me know if you find out. In my experience this happens in Release mode but not in Debug mode.