• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 320 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.

CODECOMPOSER: Unverified breakpoint since CCS 20.4

Congyue Zhang
Prodigy 157 points

Part Number: CODECOMPOSER

Hi CCS team,

We have been using CCS project-less debugging for our internal code base for AM263px.
Everything works fine before on 20.3.0 after we properly configure the symbol path in launch.json.

However on 20.4.0 or 20.4.1, any breakpoint we set from source code view will become "unverified breakpoint" and no longer take effect. 
We have confirmed every single line is having this issue, so it's not related to code optimization etc.

And pausing the code can properly halt the execution at certain source code line. So the symbol itself is loaded properly.

We could still add break point from disassembly view, but it was not as convenient as from the source code.
image.png

Could you help take a look and advice workarounds or provide fix in future versions?

Thanks,
Congyue

  • 0
    TI__Guru**** 483431 points

    Hello Congyue,

    This may be related to a known issue impacting project-less debug sessions.

    https://sir.ext.ti.com/jira/browse/EXT_EP-13180

    Have you moved the *.out and source files outside the original project folder?

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 157 points

    Hi Ki,

    No we didn't change the file structure recently, and actually the same code base + launch.json/am263px.ccxml configs works for ccs12.8 and ccs20.3, but not ccs20.4.x, which probably indicates a regression on CCS.

    In launch.json we do have "sourceDirs" specified properly to point to the source root and "program" specified to the symbol/out file.

    The issue you linked seems to be relevant!

  • 0 in reply to Congyue Zhang
    TI__Guru**** 483431 points
    Congyue Zhang said:
    No we didn't change the file structure recently

    The question is if the *.out file does not reside in the file it was originally generated in. I believe there was bug in 20.4.x where if the *.out files was moved from the original location in was generated (i.e. the project build configuration subfolder - if you using CCS projects), then source breakpoints cannot be properly resolved while this worked in earlier versions. So even though you didn't recently change the directory structure, what worked in CCS 20.3 no longer works in 20.4.

  • 0 in reply to Ki
    Prodigy 157 points

    Hi Ki,

    Thanks for the explaination! But for project-less debugging, I don't know how to find out the expected build directory expected by CCS.

    Our build system should generate the out file without moving it.
    I have tried to move my symbol file (i.e. out file) to multiple locations like the code base root, output root etc., none of them work for me.

    Is there a way to find out the expected build path so I can manually copy the file as a workaround? Can I get that from launch.json or the symbol file content?
    Otherwise I will wait for the fix in the next release.

  • 0 in reply to Congyue Zhang
    TI__Guru**** 483431 points
    Congyue Zhang said:
    Otherwise I will wait for the fix in the next release.

    It will be fixed in the next release (20.5.0). However, there is a patch available. If you are interested, please start a private E2E conversation with me for more details.

    Thanks

    ki