• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 547 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 3.3 linker error message

ran35366
Genius 12805 points


Customer runs CCS 3.3 with Code generation tools 6.0.19 

Customer build applications using object library (decoder library)

 

The customer was able to build a previous project with the same library and run it on the simulator.

 

In his new project he gets the following linker error:

>> application error: die_ref (0094d53e) does not match section position

                      (0094d53f)

 

[0094d53e] DW_TAG_TI_reserved_3

 DW_AT_low_pc 0xef719596

 DW_AT_TI_reserved_8 true

>> fatal error: cannot continue; aborting

 

I understand that it might be a linker error, and the solution is updating the tools.

 

1.     Is it true?

2.     What is the nature of the error?

Thanks

  • TI__Guru**** 251230 points

    ran said:
    I understand that it might be a linker error, and the solution is updating the tools.
     

    1.     Is it true?

    Yes.

    ran said:
    2.     What is the nature of the error?

    I don't know exactly what is wrong.  It has something to do with the handling of the Dwarf debug information.  If you don't need to debug or profile this build (unlikely, I know), then you can rebuild all the C source with the option --symdebug:none.  Because you still have Debug information in your libraries, that step may not avoid the issue.  But there is a good chance.

    Thanks and regards,

    -George

  • in reply to George Mock
    TI__Guru**** 251230 points

    I just noticed your customer is using the relatively old v6.0.19 compiler tools.  Is it possible that this decoder library was built with a more recent version of the compiler, say v6.1.x or v7.2.x?  If so, that would explain this error.  In that case, the old v6.0.19 linker is seeing some new Dwarf construct or organization that is introduced in v6.1.x or v7.2.x.

    Thanks and regards,

    -George