• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 3768 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.

CCS: Prevent redundant build when entering debug

Cool Javelin
Expert 1680 points

Tool/software: Code Composer Studio

CCSv6, Win7 SP1 32bit.

My normal debug style is:

Compile my project (click on hammer)

Enter debug (click on little spider)

Find error

Exit debug (click red square [shouldn't that be a stop sign?])

Fix my code.

Repeat.

After I build, and when I click debug, CCS redundantly builds again. How do I stop that?

I can edit my code then click directly on debug and it builds, but if there is an error CCS goes into debug mode but may not load my code.

At that point there is no way to exit the debug mode (red square disabled.) I must fix any code errors and click the hammer again.

Thanks, Mark.

  • 0
    TI__Guru**** 463901 points

    Hello Mark,

    Cool Javelin said:
    After I build, and when I click debug, CCS redundantly builds again. How do I stop that?

    It is available in the workspace preferences:

    Once comment about your debug style:

    Cool Javelin said:

    My normal debug style is:

    Compile my project (click on hammer)

    Enter debug (click on little spider)

    Find error

    Exit debug (click red square [shouldn't that be a stop sign?])

    Fix my code.

    Repeat.

    Why do you exit debug to fix your code? It may be more convenient to leave the debug session running and simply fix your code and rebuild. If the rebuild is successful, the debugger will detect that the code has changed and ask if you wish to reload the program. This will be quicker since the debug session doesn't have to be launched again.

    Thanks

    ki

  • 0 in reply to Ki
    Expert 1680 points
    Yes, one can just do a rebuild from within the debug state, but there is a bug in that:

    If an error is introduced, the compiler won't make an out file. When that happens, there is no way to exit the debugger. The debugger is left in some kind of middle state where it isn't in debug, but doesn't exit either. You can't exit the debug state because the red stop button is grayed out.

    Once this occurs the only solution at that point, is to 1)fix the error and recompile, 2)quit Code Composer and restart.

    Rather, I find it is more reliable to exit the debugger, recompile, then reenter the debugger.

    Mark.