• State
  • Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 2073 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

Getting a stack trace postmortem

Graham Hudspith
Prodigy 140 points


Hi All,

This is a fairly basic question, so I'll be more than happy for someone to tell me where to find this information in the documentation !

How can you get a stack trace from a program which has aborted ?

I've a program running on an evm6670 (using CCS 5.0.3 and SYS/BIOS 6.32.01.38) which has aborted:

 

 

How can I make this into a more useful stack trace ?

I've had a read of the SYS/BIOS FAQ (see http://processors.wiki.ti.com/index.php/SYS/BIOS_FAQs#4_Exception_Dump_Decoding_Using_the_CCS_Register_View) and that mentions about "all of these exception handlers print a complete register context dump to the CCS console" followed by instructions for using this data to get a stack trace.

I've added use of 64p.Exception in my RTSC config file, re-built and re-ran the app, but no such output can be seen on the console:

[ Obviously, I can work out what is going wrong in this instance (I'm freeing a MessageQ message using a DDR3 heap id) ]

Is there something else I have to enable or configure ?

Thanks for any hints,

Graham.

 

  • 0
    TI__Mastermind 45025 points

     

    Hi Graham,

    My apologies for the lack of response, your message has apparently slipped through the cracks and was just brought to my attention.

    The reason that you don't see any of the register dump info is because you are hitting an assertion; the register dump is only supported for exceptions.

    The best way to debug this issue is to use break points.  You will need to put a break point at the line mentioned in the error message.

    However, in order to do that you would need to enable a custom library build of SYS/BIOS (by default, the libraries are built in release mode and so do not have debug symbols in them).

    Please see this FAQ for more on how to do this:

    http://processors.wiki.ti.com/index.php/SYS/BIOS_FAQs#1_Making_a_debug-able_Custom_BIOS_Library

    Steve