Debug mode and Break Points
-
Does this make sense? When I enable breakpoints, the code at the breakpoints gets executed and things appear to work as expected. When I DON’T ENABLE breakpoints, the code at the breakpoints DOES NOT get executed. It doesn’t make sense that enabling/disabling breakpoints would control if a piece of code is reached or not. I'm debugging an MFC app I created in VS2005. I am running the DEBUG version and attaching to the process. When I disable the breakpoints, nothing happens (I have used message boxes/print statements in place of breaks to see if code reached.)
-
Does this make sense? When I enable breakpoints, the code at the breakpoints gets executed and things appear to work as expected. When I DON’T ENABLE breakpoints, the code at the breakpoints DOES NOT get executed. It doesn’t make sense that enabling/disabling breakpoints would control if a piece of code is reached or not. I'm debugging an MFC app I created in VS2005. I am running the DEBUG version and attaching to the process. When I disable the breakpoints, nothing happens (I have used message boxes/print statements in place of breaks to see if code reached.)
john john mackey wrote:
I have used message boxes/print statements in place of breaks to see if code reached
It could be possible that message boxes are unable to be created. Why don't you instead try using
OutputDebugString()? Are you sure this is not a problem with Debug/Release builds?Waldermort