Perhaps it MAVs, perhaps not. But your data will for nearly sure be bogus, because you have to know why you do such trash in your code, not Windows.
Which means: don't write on references you haven't initialized or be aware that you are doing something highly critical (and stupid)
Windows will throw a MAV if you try to access / modify data that does not exist (after file load) or which you aren't allowed to access (kernel memory and protected memory, as well as trying to access your apps code in memory which is forbidden as well)
As mentioned above: Use debug mode, this will show you all errors.
And step back from using Ptr within BM. They exist, but they are not the prefFered nor the stable way of using BM. References are similar to pointers, but they are type safe and managed and thus will never lead to problems like the one were are actually talking about here.
Thats something thats more or less a C++ hacker problem (hacker because one thats programs this way in C++ can't be seen as a programmer even on noobish level)
Which means: don't write on references you haven't initialized or be aware that you are doing something highly critical (and stupid)
Windows will throw a MAV if you try to access / modify data that does not exist (after file load) or which you aren't allowed to access (kernel memory and protected memory, as well as trying to access your apps code in memory which is forbidden as well)
As mentioned above: Use debug mode, this will show you all errors.
And step back from using Ptr within BM. They exist, but they are not the prefFered nor the stable way of using BM. References are similar to pointers, but they are type safe and managed and thus will never lead to problems like the one were are actually talking about here.
Thats something thats more or less a C++ hacker problem (hacker because one thats programs this way in C++ can't be seen as a programmer even on noobish level)