breakpoint skip

[Daniel1956]

I've got a problem with debug, where it skips my breakpoint in my code.
I've deactivated global interrupts,
I don't use goto.
I use pic16F1789 with CCS compiler V 5.070.

Any ideas about a possible cause?

Thanks in advance for the help.
Daniel

[Ttelmah]

What IDE?. What actual debugging tool?. Is the code actually running?.

Not reaching a breakpoint can be caused by several things:
1) Most chips only support a limited number of breakpoints. There is a
warning if this is exceeded, but this can be disabled. Extra breakpoints
then won't work.
2) Chip could be watchdog restarting, so not reaching breakpoints.
3) The IDE will sometimes fail to properly load the debug executive
can be caused by just a little extra capacitance on the lines. The
programming used to write this is slightly different from normal programming
so an error is not given, but this then stops all of the executive from
working correctly (this one is a real b&*&ard).
4) MPLAB-X can sometimes get itself 'hiccuped'. A full restart, recompile
and reprogram will usually fix this. Have not seen the same with the CCS,
IDE but it does sometimes give some lesser oddities that a restart clears.
5) If using MPLAB-X, clear the cache. 'help' - > 'about' tells you where
this is. Corrupted values in here can stop the IDE from working right.
6) Sometimes code lines do not actually have corresponding code. So
a breakpoint cannot actually be generated to them. Normally the IDE
will warn if it can't resolve the line, but again this can be turned off.

It is often easier to generate a deliberate 'nop' line to be the target
of a breakpoint. So add a line:

delay_cycles(1);

to your code, and break on this. Makes sure there is actually code there
for the IDE to generate a break 'on'.