CCS issues to watch local variables

Do you have full optimization (-o3) enabled on the project? I have seen cases where lowering the optimization level while debugging will make it more practical to view things like local variables, since -o3 can move the code around in ways that it no longer aligns with the source you are trying to debug.

I do NOT have the full optimization (-o3) enabled on my project.

The Opt Speed vs Size : Speed Most Critical (no -ms)

The Opt Level of my project is None

The progarm Level Opt is also None

Sounds like something is messed up in your CCS.  Rather than do hours of debugging it might be faster to just uninstall/reinstall.  Alternatively you might try applying the latest service release if it has not already been applied.  Perhaps that will fix whatever is wrong.  When you do the reinstall turn off your anti-virus if possible.

Brad

In fact, our co-workers have the same issues as I have. They could make the local variable checking either. So, this does not look like it messed up my CCS only.

Then it's probably some kind of anti-virus or anti-malware interfering with the installation and affecting all of you.

Can they use local variables with another project? Are you all trying to see the local variables of a specific project?

Yes, it is the same project.

This is inspiring.

I just tested another project, in which, I CAN get the local variable value in the watch window without problem. I compare the build option between these two projects and they are the same. The only differnce is the first project is much complicated and with a lot of source code from different .c files. Other than this, I do not have any clue what caused the diffent debugging result using Watch Locals.

If the variables are stored on stack, could there be problem of stack size?

Renaissance said:

If the variables are stored on stack, could there be problem of stack size?

If you were running out of stack space I would expect more of a system crash as opposed to the variables just not being visible, I do not know of any limitations of the variable viewer in regards to supported maximum stack size (as far as I know it does not care about stack size), though this would make sense as the major difference with a larger project.

Yeah, your project should not be working properly if it is a stack problem. You could try increasing it. If you are using DSP/BIOS, remember that TSKs have their own stack (they do not use the system stack), so if the problem is occurring in a TSK, you have to increase the TSK stack (at the TSK properties).

Also, comment the printfs if you have them for now, they use the stack and could be the reason you are running out of stack space.

I never modify the stack size before. Can you give me a hint on how to adjust the size of stack in CCS?

I just found in the Build Options, in the Linker Tab, there is a setting for Stack Size. But how could I know the current stack size, so  that I can use a larger setting?

Thank you

Are you using DSP/BIOS?

No. I do not use DSP/BIOS. My current project is running on C6455 DSK board.

So your stack is defined in the .cmd file added to your project. There is probably a line:

  - stack 0x2000

just change the size there.

You can also set the stack size in your linker options.  There's a field for stack size and heap size.  Note that if you specify both here and in the command file that it will get over-ridden by the command file.  If you don't specify in either place it defaults to 0x400.

Current setting is

-c
-heap  0x8000
-stack 0x8000

I just change -stack 0xF000. After I rebuild it, it still does not work

Well, I'm out of good sugestions...

- disable all optimization levels, look for broken pointers, increase stack, etc.

We know that it is something particular to the projects, not CCS because it works for simple projects...

If you want, send us a test case where the local variable view does not work for you.

I'm glad to hear that, thanks for the feedback!