Hi, yesterday we updated to a new version of some middleware we are using, and had a very bizarre merge problem with perforce... it had created approximately 10-20 thousand lines of white space in one of my functions, this all compiled fine, upon running the program it crashed indicating some memory issue, tracing back through the call stack I discovered visual studio was pointing the debugger right into the middle of the function that had the thousands of lines of white space in it, deleting the excess lines and recompiling fixed this issue, I was just wondering how this is so?, there was no difference in the code and the compiler is supposed to ignore all white space, is this some kind of bug in visual studio?
thanks