Reynard 0 Posted October 24, 2007 Report Share Posted October 24, 2007 Pressing Step Into or Step over causes debugger to run forever after a couple of steps. Program should just loop in single step mode forever for each button press. #include <system.h> unsigned char ucTest; bool bTest; void main(void) { bTest = false; for (; { if (bTest) { ucTest = 1; } } } Also, pressing the reset button (after stopping run forever) does not reset the debug cursor to the first instruction. Using: BoostC & IDE 6.81 Windows XP Pro SP2 PIC16F873A Cheers Reynard Quote Link to post Share on other sites
Pavel 0 Posted October 25, 2007 Report Share Posted October 25, 2007 Pressing Step Into or Step over causes debugger to run forever after a couple of steps. Program should just loop in single step mode forever for each button press... See no problem here. The code loops around 2 assembly instructions that both belong to the same source code line so there is no opportunity for execution line to advance to any other source code line. That's why it looks like stepping takes forever. Regards, Pavel Quote Link to post Share on other sites
Reynard 0 Posted October 25, 2007 Author Report Share Posted October 25, 2007 Pressing Step Into or Step over causes debugger to run forever after a couple of steps. Program should just loop in single step mode forever for each button press... See no problem here. The code loops around 2 assembly instructions that both belong to the same source code line so there is no opportunity for execution line to advance to any other source code line. That's why it looks like stepping takes forever. Regards, Pavel And there was me thinking it would step through the lines of source code including the for (;. Doh ! Cheers Reynard Quote Link to post Share on other sites
Recommended Posts
Join the conversation
You are posting as a guest. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.