• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 101 subscribers
  • Views 257 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.

Source lookup for xdctools files

Grant Freese
Intellectual 700 points

I'm trying to debug an issue in a TI-RTOS project that ends up an abort() in exit.c.

The problem is that when the RTS source library is present in the debug source lookup path, the wrong files will be opened when I double click on them in the debug callstack menu.

For example, double clicking on:

xdc_runtime_Assert_raise__I(unsigned short, char *, int, unsigned long)() at Assert.c:34 0x3E0076

will open c:\ti\ccsv6\tools\compiler\ti-cgt-c2000_6.4.4\lib\src\Assert.c, and it will show the active line pointer in a comment.

If I remove the RTS source library from the source lookup, it will fail to find the file, and will report that it actually wants:

/db/rtree/library/trees/xdcprod/xdcprod-t52/product/xdccore/Linux/xdctools_3_30_04_52_core/packages/xdc/runtime/Error.c", which is in the xdctools. 

Question: Pointing it to the correct file every time is tedious. Is there any easy way for it to find the xdctools files automatically?

  • 0
    TI__Mastermind 37985 points
    Grant,
    do you have the directory <XDCtools installation>/packages in the debug source lookup path? Also, I don't see any mention of "Error.c" in the first message, but then CCS is looking for "Error.c" in the second message. Is the second message also displayed when you clicked on xdc_runtime_Assert_raise__I?
  • 0 in reply to Sasha Slijepcevic
    Intellectual 700 points
    Whelp. I copy/pasted the wrong one on the second line. It's still looking for Assert.c in the same directory as the one I pasted with Error.c though.

    How do I actually add <XDCtools installation>/packages to the source lookup path? I'm trying to in the debugger configuration menu, but file system directory appears to be the only option that lets me type in a path, and it will not accept "<XDCtools installation>/packages" as a path.
  • 0 in reply to Grant Freese
    TI__Mastermind 37985 points
    I was using <XDCtools installation> as a placeholder for the actual file system path. If you installed in a default directory, it should be C:/ti/ccsv6/xdctools_3_30_04_52_core/packages.