Forum Discussion
Altera_Forum
Honored Contributor
Honored ContributorUnexpected breakpoints
I have recently build up a section of my code, added a task to the system and now I am not able to run the software at all. The debuger stops every moment on modules like alt_irq_handler and ot...
Altera_ForumHonored Contributor
Honored Contributor --- Quote Start --- originally posted by david_cai@Oct 8 2006, 11:46 PM is there any "break" instruction near the breakpoint?
altera's hal api set many "break" instruction in the apis
in case of unexpected things happen. --- Quote End --- Does not look like there is any conditional break there... First time my program stops, it stops at the SIGTRAP Trace/Breakpoint at the first line (opening brace) of the function alt_irq_handler in the alt_irq_handler.c module. So I press green arrow RESUME button, and instantly program stops again, in the same task# 1 at the same line of the code: entry to alt_irq_handler(). So I press RESUME button again, and the code stps in the same task1 in the function alt_tick of the alt_tick.c module... Next time it stops is in the os_core.c module, line 532, and debugger does not find the source file but the function name indicated in the debugger window is OSTimeTick(). So I press RESUME to have more fun, and my code stops at the entry to alt_tick function again. And then at the OSTimeTick() again, then alt_tick() and so on... Looks like each and every system clock tick causes the breakpoint and the code is unusable. My "breakpoints" window is empty, no breakpoints set, even no defined & disabled ones... Please help! What can I do ? How to troubleshoot in such situation ?
