AnsweredAssumed Answered

CodeWarrior 8.3 does not stop at watchpoint

Question asked by Graeme H on Oct 7, 2016
Latest reply on Oct 13, 2016 by ZhangJennie

I am trying to debug an issue on the MC56F8366 using CodeWarrior 8.3.

 

Before running the program, I have set a up a watchpoint to stop the debugger each time variable is written to. Initially this appears to work as the variable is written to multiple times during the program initialisation and the debugger stops at each one. On the final stop the value of the variable is set to 1.

 

I then run the program and there are no stops until after the issue which I am debugging has occurred. I then manually halt the program and examine the value of the variable, which has changed to 0.

 

For some reason the watchpoint did not trigger when it was changed. Why would this happen? Is there anything I can do to avoid it?

 

As far as I can see I have set up a permanent watchpoint. One thing I have tried is to clear the watchpoint on the final stop during initialisation and then set it again before restarting execution.

Outcomes