Word for a logic path execution counter?

Hello, I'm proposing a debugging/profiling technique in which we set up some add'l variables that count the number of times a certain logic path is executed within  our code.

For reasons I won't bore you with (I'm trying to persuade people to make a little effort to use these), I feel like what I call this type of variable will be important.  


I feel like there is some computer-science-y technical term out there that I should be using, but otherwise I'd like to think of a snappy term that immediately calls to mind its purpose (whether literal or by analogy).

(Oddball question I know, but you guys have generally knocked these out of the park.)

Who is Participating?
TommySzalapskiConnect With a Mentor Commented:
Any reason you are building these variables into your code instead of using a profiler that does all that for you? There are many profilers out there already and you won't have to worry about corner cases where you forgot to put your counters.

Off the top of my head, I'd call them "iteration counters."
aburrConnect With a Mentor Commented:
path tracker
d-glitchConnect With a Mentor Commented:
These are frequently called loop counters
A proven path to a career in data science

At Springboard, we know how to get you a job in data science. With Springboard’s Data Science Career Track, you’ll master data science  with a curriculum built by industry experts. You’ll work on real projects, and get 1-on-1 mentorship from a data scientist.

RonMexicoAuthor Commented:
Thanks for the good responses, I'll keep this open a bit.

@TommySzalpaski: interesting, do they have these for straight embedded C programming (no OS)?  Or are they debugger based?  I'm thinking about something that is always in there, and you can query these values via a serial port at any time.  But I'd like to look into profilers, for sure.
TommySzalapskiConnect With a Mentor Commented:
There are some that are designed to work in embedded environments. I did a Google search for "embedded C profiler" and saw several promising links. One of the articles is from someone describing how he made his own
If one of the off-the-shelf ones (like embeddedprofiler.com) doesn't work, you could try that approach. It would be a lot better (in my opinion) then trusting all the developers to add the right "event counters."
phoffricConnect With a Mentor Commented:
For some of my projects we purchased a product that would "instrument" all or parts of our source code files (our choice) to perform run-time checks. Immediately after each compilation, the source code was restored to its original state. Generally, unless there is a strong need, the instrumented code should be removed when programs go into production. (This was especially true for embedded real-time boxes.)
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.