It seems that you are mixing object files built with different settings. Try to do a full clean rebuild and check all project file settings to make sure that the _ITERATOR_DEBUG_LEVEL macro is the same (e.g., you are not mixing debug and release built objects).
More Related Contents:
- Debugging with command-line parameters in Visual Studio
- View array in Visual Studio debugger? [duplicate]
- How to display a dynamically allocated array in the Visual Studio debugger?
- Automatically adding Enter/Exit Function Logs to a Project
- Is there a way to automatically avoiding stepping into certain functions in Visual Studio?
- Template instantiation details of GCC and MS compilers
- x86 MUL Instruction from VS 2008/2010
- What are data breakpoints?
- Inspecting STL containers in Visual Studio debugging
- “Step over” when debugging multithreaded programs in Visual Studio
- C++ Reading an unknown number of integers to cin and outputting the sum
- Why does .NET add an additional slash to the already existent slashes in a path?
- Where does Visual Studio look for C++ header files?
- How to track down a “double free or corruption” error
- Displaying the #include hierarchy for a C++ file in Visual Studio
- Export all symbols when creating a DLL
- How to build Qt for Visual Studio 2010
- How to redirect qDebug, qWarning, qCritical etc output?
- Atomic operations, std::atomic and ordering of writes
- What do C and Assembler actually compile to? [closed]
- Linking dll in Visual Studio
- Understanding return value optimization and returning temporaries – C++
- What issues can I expect compiling C code with a C++ compiler?
- How to declare a global variable in C++
- Heap corruption under Win32; how to locate?
- How are GCC and g++ bootstrapped?
- constant variables not working in header
- Using Visual Studio project properties effectively for multiple projects and configurations
- F5 or Start Debugging Button is Greyed Out for Winform application?
- Debug Assertion Failed! Expression: _BLOCK_TYPE_IS_VALID [closed]