Debugger jumps into memcpy.asm

[Martin_B_2]

I am just going through my program in debug mode. Currently I have the problem, that when a value is assigned to a variable, the debugger jumps into  memcpy.asm. I don't want to see this!

I think there's a project property set wrong, but which one?

[mecej4]

We would need to see the build-log file to know.

I think that this happens because one of the libraries (that you linked to when you built your program) contains debug symbols. Examples are libifcoremdd.lib and libcmtd.lib, and such libraries are selected if you used compiler options such as /MDd.

[Steven_L_Intel1]

Perhaps you are using "step into" rather than "step over"? If so, that means you'll step into any library routines used to support your code.

[DavidWhite]

Steve,

The issue is that I want to be able to step into my code, but not into any assembler.  I want to make sure I step into any of my subroutines, so normally use Step Into all the time.  But then I never know when one of the asm routines will get stepped into.

Along time ago (3-4 years), this seemed to be the only thing I needed to do to step through my code one line at a time.  Now I need to remember to Step Into on some lines, and Step Over others.  It was much simpler before.

David

[IanH]

You can tell Visual Studio, unofficially, to always step over particular procedures.  See http://blogs.msdn.com/b/andypennell/archive/2004/02/06/69004.aspx for details, read to the end of the post for details for later Visual Studio versions and being mindful of registry redirection if on 64 bit windows.

[Steven_L_Intel1]

Nothing has changed in this regard since I started using Visual Studio in 1997. What you may be seeing is that the compiler is able to recognize more operations that can be done with optimized library routines, but there will always be library calls in your code. You can use "step out" if you find yourself in one, or be more selective in using Step Into.