• State Not Answered
  • Locked Locked
  • Replies 13 replies
  • Subscribers 19 subscribers
  • Views 13418 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

"Out of scope" variables on debug

Alex Garcia

Hi all,

I'm having a very troubling problem when debugging with the new version of µvision (4.11) that I didn't have with the last I was on (it was 4.03 I think). When I debug code on various platforms (working on an STM32F103 and an NXPLPC1768, both CM3), I have a lot of variables that appears "Out of scope" in the watch window.

I'd like to add that I'm at optimization level 0, I tried default but it optimized more and I had even less variables visible, and that this problem did NOT happened with the previous version of the software.

Thank you in advance for you answers.

Parents
  • 0

    The optimizer removed the variable bar since you do not do anything with it. It is initialized but left unused, so all code related to the variable is removed.

    You can either

    • Do something with the variable.
    • Declare the variable as volatile, which stops the compiler from optimizing code related to the variable out. For example: 
      volatile unsigned char bar;
Reply
  • 0

    The optimizer removed the variable bar since you do not do anything with it. It is initialized but left unused, so all code related to the variable is removed.

    You can either

    • Do something with the variable.
    • Declare the variable as volatile, which stops the compiler from optimizing code related to the variable out. For example: 
      volatile unsigned char bar;
Children