Code jumps over new function call

[skinnedknuckles]

I added a file "new.c" to my project and moved several functions from "old.c" to "new.c".  I also created "new.h" with the prototypes of the function names I moved and added   #include "new.h"   to the top of both files.  When I run my program, the code execution has no trouble moving to the function in "new.c" called from "old.c" but but literally skips or jumps over calls to other function calls within "new.c".  I can set a breakpoint on a call to a function in "new.c" normally.  But as soon as the program executes, the break point literally moves down to the next executable line in "new.c".  When program execution ends, the breakpoint jumps back up to the function call.  I think it must be something simple I'm doing wrong but I don't know what it is.

[skinnedknuckles · Accepted solution]

I think I found the problem.  I was using a local structure as the type for the input argument of the function in question.  I guess it didn't like that.