• State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 22 subscribers
  • Views 1644 views
  • Users 0 members are here
Options
Related
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

uVision debugging 'Watch' question

HenkvW

Hi,

I'm using the Keil uVision V4.03q.

I wonder if there's any setting to be able to watch all variables during debugging?
If I want to watch a function argument in a function it says: 'out of scope' so I have to define a static copy of that variable to be able to watch it

Optimization is set to minimum level.

Thanks

Henk

Parents
  • 0

    Not sure if it's worth the effort but you can record the variable access.
    At the point where the var is used (changed) you can do a breakpoint execute to call a debugger function.
    Then write a simple debugger function to printf() the var.
    The printf()in a debugger function is not the printf() to a serial port. This printf() only writes to the command screen in the debugger. See the debugger manual for examples.
    When the breakpoint executes, the var will be printed to the command screen but the code will continue. In other words a breakpoint execute does not stop the code. You can go a little further and log the command screen to a file for some later perusing. Only you can define if it's worth the little effort.

    Bradford

Reply
  • 0

    Not sure if it's worth the effort but you can record the variable access.
    At the point where the var is used (changed) you can do a breakpoint execute to call a debugger function.
    Then write a simple debugger function to printf() the var.
    The printf()in a debugger function is not the printf() to a serial port. This printf() only writes to the command screen in the debugger. See the debugger manual for examples.
    When the breakpoint executes, the var will be printed to the command screen but the code will continue. In other words a breakpoint execute does not stop the code. You can go a little further and log the command screen to a file for some later perusing. Only you can define if it's worth the little effort.

    Bradford

Children
No data