This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Some variables in program gets corrupted

Other Parts Discussed in Thread: TM4C1290NCPDT

Hello all,

I am using CCS v6.0.1 with compiler version Tiv5.1.11, and using TM4C1290NCPDT controller,

In debug mode if i run and pause the program then sometimes some of the variable gets corrupted with unknown value. It happens some times. It is a high risk problem need to address immediately so guys please help me out.

I didn't try this on release mode as i have to observe these values and we are in  final stage of the project. I am afraid if it happens in release mode also.

Please support

  • A stack overflow seems rather improbable, spurious crashes would be more likely in this case.

    Most probably this is caused by bugs in your (undisclosed) software. When hard-pressed for a guess, I would tend to an array index out-of-bound.

    I am afraid if it happens in release mode also.

    That depends on the differences between your debug- and release build, but I would bet so.

    I would try data watchpoints. Support for those advanced debugging depends on your (undisclosed) toolchain and debug adapter.

  • Bravo to poster f.m. for his highlight of (undisclosed) code specifics and/or issue examples.

    The entire code need not be presented - yet (some) illustrations/examples would seem an obvious aid to poster's forum "staff."

    As presented - may I challenge your representation of being, "In the final stage of the project?"   With such multiple, undiagnosed, destructive issues I submit that you are FAR SHORT of (any) "Final Stage!"   Firm/I often note that such unresolved issues - left to fester to the, "final stage" - most always prove both difficult & expensive to find & correct.

    KISS teaches that code should be modularized - properly/fully debugged & test/verified individually - and then (systematically & gradually) introduced to the full program.   As presented here - the identification of each/every issue has been rendered highly complex - and that (likely) could have been avoided.

  • Hello Ashish,

    What program are you executing on the device? Is there static allocation or dynamic allocation of memory?

    Regards
    Amit