This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Multiple "Next Statement" Arrows in Debug Session

I'm working with some code running on an LPC2378-based board. I'm attempting to JTAG debug the target using uLink2. When I'm stepping through code, however, program flow doesn't seem to follow the path I think it should and multiple "next instruction" arrows are often shown (though one is yellow and one is light blue). I've tried looking through the uVision4 documentation, but can't find any reference to a light-blue arrow or any hint at its meaning.

I've used DK-8051 previously for some 8-bit work and never seen this behavior. I'm new to MDK-ARM and have been foiled a bit in trying to figure out what's going on. Any insight would be greatly appreciate.

Parents
  • Playing around with it the Cyan arrow seems to be a mulit-purpose arrow

    If you do a find in files search, and double click on an entry in the "find in files window", the cyan arrow points to the appropriate line.

    If you get a double click on a warning in the output window, the cyan arrow points to the appropriate line.

    If you have the dissasembly window open as the active window, where ever the yellow bar is in the dissasembly window, there will be a cyan arrow pointing to the appropriate line in the C source.

Reply
  • Playing around with it the Cyan arrow seems to be a mulit-purpose arrow

    If you do a find in files search, and double click on an entry in the "find in files window", the cyan arrow points to the appropriate line.

    If you get a double click on a warning in the output window, the cyan arrow points to the appropriate line.

    If you have the dissasembly window open as the active window, where ever the yellow bar is in the dissasembly window, there will be a cyan arrow pointing to the appropriate line in the C source.

Children
No data