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.

CCSTUDIO: Segmentation Fault After Loading Application Prior to Debug Session

Part Number: CCSTUDIO

Hello,

I have recently encountered a strange issue with CCS 11.2.0.00007 on Ubuntu 20.04 where it crashes (segfault) immediately after loading a program that I'm trying to debug on custom hardware via an XDS110.
This problem started happening out of the blue, and it only affects one of my projects.

I have attached the .log file from the .metadata directory: /cfs-file/__key/communityserver-discussions-components-files/791/ccs.log

Here is a link to the coredump: core._opt_ti_ccs1120_ccs_eclipse_ccstudio.1000.1bb7a079-86b7-4975-a3f8-bb84fa3ff1c5.26700.1678584.xz

Let me know if there are any other logs that I should provide.

Peter

  • Hi Peter,

    Which device are you working with?

    Would it be possible to share the executable with the issue? (we can share via private E2E messaging)

    Thanks

    ki

  • Ki,

    We are using the CC1352R1F3. I will send you the executable via direct message.

    Thank you,

    Peter

  • Thank you for the executable. I can reproduce the issue on both Linux and Windows and with both CCS 11.2.0 and CCS 12.0.0. I have filed a bug for this. Tracking link: https://sir.ext.ti.com/jira/browse/EXT_EP-10863

    Note that there is a workaround. Please see the tracking link for more details.

    Thanks

    ki

  • Ki,

    With the workaround described on EXT_EP-10863, it appears that CCS is only loading some of the symbols from my program. Any idea why that might be or how it can be fixed?
    If I try the same procedure on a different project, the workaround is successful and I can see all of the symbols in the Modules view.

    Peter

  • it appears that CCS is only loading some of the symbols from my program. Any idea why that might be or how it can be fixed?

    The root cause of the bug is with the generated debug symbols from the compiler. The defualt "new" symbol manager with the CCS debug is unable to handle this exception and crashes. The workaround will force the debugger to use the legacy "old" symbol manager. This symbol manager can handle the exception and just ignore the invalid debug symbols instead of crashing. But because there are still issues with the symbols itself, that would prevent seeing all the symbols loaded.

  • For anyone else who is interested, I was able to resolve the issue by downgrading from TI CLANG v2.1.0 to v1.3.1.

  • Thank you for the update!