[EXT_EP-9318] pdd tool fails when program includes unused file Created: 04/Apr/19  Updated: 19/Feb/20  Resolved: 04/Apr/19

Status: Fixed
Project: Embedded Software & Tools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Medium
Reporter: TI User Assignee: TI User
Resolution: Fixed Votes: 0
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Product: Code Generation Tools
Internal ID: CODEGEN-6132
Forum URL: https://e2e.ti.com/support/tools/ccs/f/81/t/781825
Found In Release: C2000_20.2.0.beta
C6000_8.2.0
C2000_18.1.0.LTS
C6000_8.3.0
ARM_18.12.0.LTS
ARM_18.1.0.LTS
MSP430_18.1.0.LTS
C2000_19.6.0.STS
ARM_19.6.0.STS
MSP430_18.12.0.LTS
MSP430_19.6.0.STS
ARM_20.2.0.beta
C2000_18.12.0.LTS
MSP430_20.2.0.beta
Fix In Release: C2000_20.2.0.beta
C2000_18.1.7.LTS
C6000_8.3.4
ARM_18.12.3.LTS
MSP430_18.1.7.LTS
ARM_18.1.7.LTS
C6000_8.2.8
ARM_20.2.0.beta
MSP430_18.12.3.LTS
C2000_18.12.3.LTS
MSP430_20.2.0.beta
Affected Platform/Device: default
Workaround: Leaving the sys_pcr.obj file out of the link command works, but it's hard to tell that that's the problem file.
Release Notes: The profile decoder, armpdd or pdd2000 or pdd430 or pdd6x, may fail when the program on which it is called includes a file whose functions are not included in the link.

In the test case given, the file sys_pcr.obj contains functions that are not called anywhere and therefore are not included in the .out file. However, due to some quirk that we have not yet isolated, the debug info for sys_pcr.obj *is* included. When the profile decoder collects its data, it uses the debug info to locate it; the faulty extra debug info points to invalid locations, causing the warnings.

We don't know yet whether the problem is with a single excluded function, more than one, or a whole file whose functions aren't included. What we have done is to make the profile decoder recognise and ignore the bogus debug info.

 Description   

pdd tool fails when program includes unused file


Generated at Tue Apr 15 19:52:44 CDT 2025 using Jira 9.12.17#9120017-sha1:aba4002bcd633f188b6a4bb5dd8a0e1f20b79ee4.