I've bumped into a strange problem. When a function is supposed to be called, VS starts executing some other code (not the actual function!) in a file called xlocal, from where other functions are called; VS then starts jumping around between a lot of different functions. Eventually, it triggers an error message to come up, which says a lot of things; here you can see the hole message: http://img121.imageshack.us/img121/3...rormessage.png
The original function call that is made looks like this:
where s is of a template class I've created.Code:s.print(0);
I've put a break point at that line, as well as a break point at the head of the function. VS has always been able to call this function before, but now it triggers an error after the function call has been made, but before the function has even been entered. Why doesn't it enter my function directly? What can I do about this? After all, VS doesn't do what I tell it to do but acts completely crazy!