• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 1086 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/TMS570LS3137: Problems with Entry/Exit Hook Options

Hugh Shane
Intellectual 565 points

Part Number: TMS570LS3137
Other Parts Discussed in Thread: CCSTUDIO

Tool/software: Code Composer Studio

I'm attempting to use the entry/exit hook functions to monitor stack usage in my program as described in SPNU151. In the process of debugging this feature, I've discovered that once I enter an entry hook function name in the "Entry/Exit Hook Options" dialog box, as shown in the image below, that I can't get rid of this entry. If I delete the entry, e.g. delete "my_entry_hook_function", the .cproject file retains the default entry hook directive, causing my build to fail.  

.cproject after I input the name of my entry hook function 

<option id="com.ti.ccstudio.buildDefinitions.TMS470_18.1.compilerID.ENTRY_HOOK.2064082480" superClass="com.ti.ccstudio.buildDefinitions.TMS470_18.1.compilerID.ENTRY_HOOK" value="--my_entry_hook_function" valueType="string"/>

.cproject after I delete the name of my entry hook function 

<option id="com.ti.ccstudio.buildDefinitions.TMS470_18.1.compilerID.ENTRY_HOOK.2064082480" name="Insert this call at entry to each function (--entry_hook)" superClass="com.ti.ccstudio.buildDefinitions.TMS470_18.1.compilerID.ENTRY_HOOK" value="" valueType="string"/>

I can work around this by manually editing .cproject but it's a nuisance and will likely trip up someone else. It should be fixed!

  • 0
    TI__Guru**** 173310 points
    Hugh,

    Which version of CCS and compiler tools are you using? I tried a quick test to reproduce this but could not, so it may be specific to a version or to your project.

    After you delete the function names in the --entry_hook and --exit_hook fields and rebuild, do you still see them appear in the list of compiler options in the build console? Could you capture the build logs with and without the option populated and send it to us? Also please provide the versions of CCS and compiler tools? I will try to reproduce it with those specific versions.
  • 0 in reply to AartiG
    Intellectual 565 points

    Code Composer Studio  Version: 8.2.0.00007

    TI ARM C/C++ Compiler  v18.1.3.LTS

    compiler options with --entry_hook specified

    compiler options with --entry_hook removed

  • 0 in reply to Hugh Shane
    TI__Guru**** 173310 points

    Hugh Shane said:
    If I delete the entry, e.g. delete "my_entry_hook_function", the .cproject file retains the default entry hook directive, causing my build to fail.

    From the screenshots, it looks like it removed the option as expected, so could you elaborate on how the build fails?
    If there is a build error, it would be helpful to see the build log. If you could save that to a text file and attach here that would be great.

  • 0 in reply to AartiG
    TI__Guru**** 173310 points

    Hugh,

    I see from your other thread here that the issue you were having was not really a build error but rather a runtime error (which also appears to be answered in the other thread). I will go ahead and close out this thread but please feel free to post a reply or update if this issue is still unresolved.

  • 0 in reply to AartiG
    Intellectual 565 points
    I'm currently unable to recreate the problem. Once I manually cleaned out .cproject, the problem seemed to go away. If the problem occurs again I'll try to document the steps that got me there but for now I guess we can call the case closed.

    Hugh
  • 0 in reply to AartiG
    Intellectual 565 points
    The run-time problem was related to but separate from the build problem. Anyway, I've resolved both.