• State Not Answered
  • Locked Locked
  • Replies 0 replies
  • Subscribers 21 subscribers
  • Views 450 views
  • Users 0 members are here
2025 survey

We are running a survey to help us improve the experience for all of our members. If you see the survey appear, please take the time to tell us about your experience if you can.

Options
How was your experience today?
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

uV2 Problem -- call via pointer

Andrew E. Kalman

I'm debugging some code and have come up against some odd behavior in uV2 -- wondering if it's a known bug or limitation, or perhaps I need to (re-)compile with some options in order for this to work. I'm using / debugging in the Cygnal C8051F005DK.

Specifically, when I single-step (using step into) in source code, it fails when I encounter a call-by-pointer, like this:

		/* start / resume task. */
		OSEndCriticalSection();
		OScTcbP->tFP();

By "fail" I mean that 1) step into does not work in C source, but does work in the disassembly window, and 2) it reverts to Run mode. If I place a breakpoint on the C-level line just before the call-via-pointer, the step into the next line will end up with me halted at the breakpoint, i.e. it runs until it reaches the breakpoint. This is the only place in the code (that I've found so far) where single-stepping doesn't behave properly. In all other places, it's fine.

0