Help!
When a breakpoint is interrupted during simulation, the program can be paused when it reaches the breakpoint position. The problem is that I want to observe the situation after a certain step in a function is executed, but double-click the breakpoint in that line, the breakpoint will all go to the left parenthesis at the beginning of the function There, step over has also been running outside the function, and I have not found the reason for a long time. Does any brother know what is going on? Ask for advice, thank you!
Margot Posted on December 2, 2020
If the conditions are not met, the code cannot run there, so the breakpoint cannot be hit.
Darryl Posted on December 2, 2020
No, the phenomenon that the conditions are not met and can't run should be the breakpoint, but because the program can't run to this place, it won't pause, but the breakpoint position should still be hit and stopped. After I hit the breakpoint, the breakpoint ran, and then the program stopped.
Joan Posted on December 2, 2020
There is a problem with the program, and the simulation should not pass.
Royal Posted on December 2, 2020
It is possible that after macro expansion and compiler optimization, the address corresponding to the breakpoint cannot be found, you can try to turn off the compiler optimization.
Elvis Posted on December 2, 2020
Just change the line, move the position, CCS is sometimes weird, the breakpoint cannot be hit.
