We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.
In my build setup, some executable C code is in files #included within other source files. When debugging the included code, Step works ok but Step Over keeps going until the next line of the file it was included from. Regardless of the included filename extension (.h, .c, or other). Is there a way to get Step Over to stay in the include-file code? As a workaround, stepping in assembly mode works but is tedious.
Yeah, that's a workaround. But not too helpful. I didn't want to clutter up the question explaining why it's useful to do that. A very common example is an inline class method. Another is a unit test wrapper that includes the code under test, without having to use special definitions for "static" and "private".