• State Resolved
  • Locked Locked
  • Replies 9 replies
  • Subscribers 54 subscribers
  • Views 559 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CODECOMPOSER: CCS 12.1 stops working during Debug/Attach session

Tommy Beckmann
Intellectual 292 points
Part Number: CODECOMPOSER
Other Parts Discussed in Thread: CCSTUDIO

Hi TI Experts,

I figured out a problem during debugging my application. It results in a complete unexpected shutdown of CCS without notification.

Equipment used:

- XDS110 Debug probe
- AM2434B
- OS: Windows 11

Steps to reproduce:

1. Software is up and running on

2. Open CCS - Lauch existing Target configuration

3. Connect to MAIN_CORTEX_R5_0_0

4. Load Symbols

5. Target is halted on the expected position.

6. Manipulate a local variable

7. Execute a single step

--> CCS closes without any user message.

It seems that there is no log entry generated (<workspace>/.metadata/.log) - the last entry is two days old:

Fullscreen
1
2
3
4
5
6
7
!SESSION 2022-11-16 07:18:16.576 -----------------------------------------------
eclipse.buildId=4.23.0.I20220308-0310
java.version=11.0.13
java.vendor=Eclipse Adoptium
BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
Framework arguments: -product com.ti.ccstudio.branding.product
Command-line arguments: -os win32 -ws win32 -arch x86_64 -product com.ti.ccstudio.branding.product
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Is there anything in CCS settings that can influence this strange behavior?

Thanks in advance and best regards,

Tommy

  • 0
    TI__Guru**** 450771 points

    Hi Tommy,

    Thank you for documenting your test case. I tried it with CCS 12.1.0 on my Windows 11 PC with my AM243x LaunchPad (via XDS110 connection). However, I was not able to reproduce the crash. Everything worked fine for me.

    Since the debugger crashed, a debugger crash dump file shoulh have been generated. Can you attach it to this thread?

    https://software-dl.ti.com/ccs/esd/documents/ccs_diagnostic-logs.html

    Also, please provide the compiler version used to build your program. Note that there were some issues with TI Clang compiler 2.x that could cause a crash. These issues should be addressed in version 2.1.2 (which does ship with CCS 12.1). 

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 292 points

    unresponsive_15_3b6c50d0-dc95-4c86-a132-8c4b33deb2ac.zip

    Hi Ki,

    thanks for the response. The generated .dmp file is attached.

    Compiler is ti-cgt-armllvm_2.1.1.LTS

    Best regards,

    Tommy

  • 0 in reply to Tommy Beckmann
    TI__Genius 16490 points

    Hi Tommy,

    Thanks for providing the requested information. The dump file unfortunately did not give us any clues.

    Would you be able to check if there are any additional dump files being created?

    I don't think you are running into this problem based on the test case you provided, but it would still be worthwhile to try the latest compiler version (v2.1.2).  The specific compiler issue is described here: https://sir.ext.ti.com/jira/browse/EXT_EP-10863

    Lastly, would you be able to generate a debug server log file using the instructions at the link Ki provided?  These files can be huge. If you need a place to upload it I can provided that.

  • 0 in reply to AndyW
    Intellectual 292 points

    Hi Andy,

    the file has ~80 MB, can you provide a storage for upload?

    Best regards,

    Tommy

  • 0 in reply to AndyW
    Intellectual 292 points

    Ok, done - let me know if I can help you with additional information.

  • +1 in reply to Tommy Beckmann
    TI__Genius 16490 points

    Hi Tommy,

    From the log, we see a step operation followed by a run operation. The debugger keeps running for a couple of minutes after the run before the log ends. You didn't mention the run in your test case so I'd like to check if that was something you initiated or whether it may have been introduced another way.

    There's another test we'd like to try as it would help us eliminate a potential source of the issue.  Would you be able to exit CCS and temporarily rename the "ctools.dll" component found in <install_dir>\ccs\ccs_base\emulation\analysis\bin to something else (say ctools.dll.bak)?  After renaming the file, please restart CCS and retry the test case to see if you notice any difference.  You can restore the DLL afterwards. Renaming this DLL effectively disables a certain class of breakpoint operations.

  • 0 in reply to AndyW
    Intellectual 292 points

    Hi Andy,

    sry I forgot to mention that in the case of the log I initiated the run before the crash.

    Thanks for your proposed tests.
    Since I have no access to my development environment today, I am going to run the test you mentioned tomorrow.

    I will come back to you with the result.

  • 0 in reply to AndyW
    Intellectual 292 points

    Hi Andy,

    it seems that I solved my issue by importing the project into a clean workspace. Since I did this I am not able to reproduce the issue any longer.

    We can close the thread here, I ask related question as soon as I observe the issue again.

    Thanks for your support and best regards,

    Tommy