• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 53 subscribers
  • Views 967 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.

CCS/CCSTUDIO: Locate File icon for seeing library C source file

Kzk
Genius 5785 points
Part Number: CCSTUDIO

Tool/software: Code Composer Studio

Hello,

In CCS v7.3, I can't refer to the C source file of the library function. When I used CCS v6.x, there was certainly an icon of "Locate File" of "Method #1" introduced in the following presentation. Please give me some advice.

http://processors.wiki.ti.com/index.php/Tips_and_Tricks_for_CCStudio_IDE

Regards,
Kazu

  • 0
    TI__Guru**** 464751 points
    Hello,
    The most common cause of this is that the included library was compiled with high optimization or without full debug symbols (or both). This would prevent the debugger from correlating the source code with the address. That is why the option to locate the source file is not available.

    Thanks
    ki
  • 0 in reply to Ki
    Genius 5785 points

    Hello Ki,

    Thank you for your information. Building Library with Debug configuration, I was able to see the "Locate File" icon and the source code.

    However, it seems that I can see the icon even if I change the compiler and linker option of Debug configuration to the same option as Release configuration. For example, deleting -g and adding -O2 in Debug configuration.

    In other words, rather than the difference in compiler and linker options, it seems to be due to the difference in Debug and Release configuration. Though I don't know what the difference is specifically.

    Regards,
    Kazu

  • 0 in reply to Kzk
    TI__Guru**** 464751 points

    Hello,

    Kazu Kon said:
    it seems to be due to the difference in Debug and Release configuration

    ah, yes. That makes sense. Each build configuration (like Debug and Release) can have its own set of project options. This includes compiler/linker options among others. Usually, the Debug configuration is enabled for debug (-g and minimal optimization, linking in debug version of libraries) while the Release configuration is built with less debug visibility. But there is no guarantee