Yeah, I would have expected that should work. Though I've never used watch breaks when Codeprobe is jumping through assembly modules.
You've got to question why it's going into them if they're not being called though? Compiled C code can sometimes generate some weird assembly...
Don't forget to disable any optimisation during compile.
I have found a problem with Codeprode that when it opens it's own screen (default) which is 1024 x 768, same as WB, instead of having the C code in the top window, it sometimes only has an assembly listing. Perhaps that only happens on larger Picasso96 screenmodes? I haven't looked into it.
Forcing it to open on the WB screen fixes the problem.
cpr -screen Workbench or add the tooltype "-screen Workbench" to the debug icon.
Give that a try. Doubt if it's related, but you never know.