I'm fixing up some serialization code that makes heavy use of C++ templates. Unfortunately, there's something not quite right with what's happening so I'm having to trace through it with the debugger to figure out what's going on.
This makes it very annoying when I tell the debugger to single step and instead it goes flying off somewhere at random, usually into the exception throw that I'm trying to find out the cause of. I can work around this by judicious use of breakpoints, but I really hate it when the debugger decides to misbehave.
*sigh*
This makes it very annoying when I tell the debugger to single step and instead it goes flying off somewhere at random, usually into the exception throw that I'm trying to find out the cause of. I can work around this by judicious use of breakpoints, but I really hate it when the debugger decides to misbehave.
*sigh*