On 11/06/2014 at 09:49, xxxxxxxx wrote:
Originally posted by xxxxxxxx
Using a matrix pointer instead of the object itself solved the problem for me.
[...]
That basically points either to a compiler bug (related to inlining your code) or (not so likely) a problem caused by excessive stack usage in the surrounding code - you can check the later by using the analyzer function of VS 2012; it will tell you if methods stack usage exceeds 16 kb (and how much it needs exactly) - although that doesn't catch problems caused by recursive calls using slightly less than 16 kb stack.
Best regards,
Wilfried