Topic : Ride still has the same errors (or I do somethig wrong ?)

Forum : Ride IDE

Original Post
Post Information Post
January 19, 2010 - 8:59am

I've started to debug my programs using newest version of Ride7. Unfortunately i encountered the same problems as with previous version. Perhaps i do something wrong or my Ride7 is not configured correctly... These include the following:

1. The watch window is always cleared at every degugging session. This is quite problematic as there are many variables in the watch window which i must add during every debugging session.
2. When new variable is placed in the watch window its value is displayed with the highest possible value (0xFF, 0xFFFF, 0xFFFFFFFF etc. depending on the size of the value) regardless of the real value. Only after performing "Step over" or "Step Into" the watches are refreshed and show other value.
3. Debugging is still very problematic (or impossible in some cases) as the local variables are displayed with wrong values. Declaring the variables with "static " directive or as global variables doesn't always solve the problem. Many variables are displayed as "undeclared symbol" or their value are not displayed at all.
The only solution is to turn all optimization off but it considerably increases compiled program size which can't fit into the FLASH then.

Post Information Post
January 20, 2010 - 10:06am
Raisonance Support Team

Hi Kekon,

Thanks for these remarks.

Indeed if your optimization level is high, variables do not have any actual storage (they remain in registers) and order of execution of source lines can be reorganized, leading to (seemingly) erratic behavior during debug.
However there is not much you can do on this. Just reduce the optimization level for the functions you debug should be fine and your project would not grow too much.

Concerning your first and second poitns we took good note of them and will implement them in Ride7 in the future.