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.

CCS/66AK2H12: Debugging c++ objects

Part Number: 66AK2H12


Tool/software: Code Composer Studio

Trying to debug object on the ARM is giving me fits.

Using: CCS 7.3,  GNU v4.9.3, XDCtools 3.32.2.25

I posted similar a while ago. Ref: https://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/629959

I get different results when trying to view objects in the Expression window. For some objects the Type is displayed correctly but the value will have ??? marks after the address and when expended the value column says "invalid member name in macro". What does that mean?

Other objects are displayed with a type void * and when I try to expand those the Value column gives me "cannot load from non-primitive location".

This is significantly impacting my ability to debug. I don't understand what the conditions are that cause the above two things to happen. The code works as designed as far as I can tell.

It seems like it has something to do with having base classes with virtual members. Even a virtual destructor. If I remove all virtual functions than the debugger seems to allow me to view the object. I'm loathed to dispense with the use of virtuals but for the trade off of being able to debug I've started doing just that.  

Can anyone offer any guidelines or suggestions? Is there something I need to configure to properly debug? Some code structure I should be avoiding? 

  • Hi Mike,
    This looks to be a bug with how CCS handles debug output from GCC. My apologies for the poor response to your original thread. I filed a bug for this, tracking ID is CCBT-2202. I will prioritize this for quick resolution

    Thanks
    ki