C ++ VS2013 Debugger breakpoint: not hit

I have a relatively simple C ++ console project that does some calculations and writes an output file. I am trying to determine why the output file does not have the correct output. Instead, I struggled with the debugger.

For some reason, I am unable to add a breakpoint after a specific line in a specific function.

All breakpoints after line 1106 until line 1214 (end of function) are not available.

EDIT: I have moved the specific code shown in the first image into a function and this does not create problems, but now I cannot break line 1079 and the end of the function. I renamed the function, but it didn't matter.

When I look at the disassembly, I notice a strange thing on line 1078:

I'm not sure if this matters, but the statement after 1078 (line 962) refers to an object named CSVData of a type string. The string is created empty, but filled with more characters at runtime. I originally thought about Stack Overflow (no pun intended), but the breakpoint is disabled when the application starts, which is long before (10-15 minutes) before the CSVData object is full.

First thought: Use the previous breakpoint. However, when I go to the next line, it brings me to a section of code that I know is not being executed (this is in another function entirely). He continues to jump in the given but not matching pattern. Please help me. I'm losing my mind on this!

I have google'd this before asking here. I've tried the following things:

• Delete all files
• Create a new Win32 console project and add only 5 headers and 5 source files.
• Resetting Visual Studio Preferences
• Disable optimization
• Uncheck "Require source files to match original version"
• Use the "Debug" configuration
• Use Notepad ++ to check EOL characters

One of the problems I thought was causing this was Intel Parallel Studio Composer XE 2015 for Fortran as it added an inline and optimization option for FPP projects. I uninstalled and restarted trying to remove any issue from this installation.

Any suggestions would be greatly appreciated. Thank.