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.

Breakpoints OK in main project, NOT in library projects

Hi,

Just installed the 4.2.5.00005 patch for CCS, and for some legacy problem i cannot upgrade to CCS 5.

I have met a problem that breakpoints cannot be set in library projects. The main project, for convenience sake called A, uses static .lib libraries built in project B, C and so on. Both A, and library projects B, C, ... are set as "debug type", and have full symbolic debug enabled. 

Googled and some forum threads saying option "--symdebug:dwarf, -g" should be enabled as was exactly the case. However, neither by double-clicking the left margin of the editor, nor by right-clicking and then choosing New Breakpoint>>Breakpoint or Toggle Breakpoint could set breakpoint in library projects, but in main executable project A it is all fine.

Looks like this:

Could this get fixed?

/////////////////////////////////////////////////////

Adding to the problem description:

Although it is not possible to set breakpoints in editor in library projects, they can be set in disassembly, and those disassembly breakpoints are functional. But setting them in disassembly is not as free as in editor and the area where I can drag the disassembly window slider bar to navigate to is much limited.

/////////////////////////////////////////////////////

Paul

  • Paul,

    When you try to set the breakpoint in the C source, is it added to the breakpoints view but disabled? Is there a little yellow icon overlayed ontop of the grayed out breakpoint icon? If so, that means the breakpoint is unable to resolve the path of your library file. You can open the breakpoints view and right clicks on the breakpoint, than select resolve path from the context menu.

  • AartiG,

    is it added to the breakpoints view but disabled?

    It was not added to the breakpoint view.

    It seems was a problem with the emulator. I no longer had the problem after doing another fresh installation of the emulator driver.

    Paul

  • OK, glad to hear the reinstallation got it working. Thanks for the update.