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

Why does Build run Debug and vice versa?

Peddler
Intellectual 365 points

Ever since I did a recent minor upgrade of CC I see annoying behavior with building/debugging.  In Debug mode, when I do a build, it now takes the liberty of running debug.  This takes over 40 seconds for just 1K bytes of obj code so I'd like to avoid doing debug runs when I just need to do a basic compilation.  I couldn't find a CC or compiler switch to prevent this.

A related issue is that I can't deduce from the help doc exactly what the following functions are supposed to do:

* Build Active Project

* Rebuild Active Project

* Build All

* Build Automatically

* Debug active proj

* Launch TI Debugger

* Debug...

* Debug Launch (button)

Could somebody please clue me in or point me to doc which clearly explains the differences?  It seems that build All builds everything in my workspace, including non-active projects?  Thx.

 

  • 0
    TI__Guru**** 420760 points

    Chris35513 said:

    Ever since I did a recent minor upgrade of CC I see annoying behavior with building/debugging.  In Debug mode, when I do a build, it now takes the liberty of running debug.  This takes over 40 seconds for just 1K bytes of obj code so I'd like to avoid doing debug runs when I just need to do a basic compilation.  I couldn't find a CC or compiler switch to prevent this.

    It sounds like you are doing a "Debug Active Project". That will do a build, and then start a debug session. You should just do a "Build Active Project"

    Chris35513 said:

    A related issue is that I can't deduce from the help doc exactly what the following functions are supposed to do:

    * Build Active Project

    * Rebuild Active Project

    * Build All

    * Build Automatically

    * Debug active proj

    * Launch TI Debugger

    * Debug...

    * Debug Launch (button)

    Could somebody please clue me in or point me to doc which clearly explains the differences?  It seems that build All builds everything in my workspace, including non-active projects?  Thx.

    The included Help in CCS ('Help->Help Contents') should explain what these mean. Under 'Tasks' in the Help content, check out the 'Debugging in CCS' and 'Working with CCS Projects' sections.

    Thanks

    ki

  • 0 in reply to Ki
    Intellectual 365 points

    Thanks, for the info, Ki, I appreciate it.  I'm not sure if you understood what I was saying.  Once again, when I say either "Build Active Project" or "Rebuild Active Project", either from the pull-down menus or using the buttons, the tool does a build AND THEN does a debug.  By "debug" I mean it does the same things it would do if I manually said "Debug" and results in the console message "MSP430: Program Loaded..." and the cursor is placed at the start of main.c in debug mode.  This process wastes 30 sec of my time.  I do not want the tool to do a debug when I tell it to do a build.  Can anyone tell me how to configure it accordingly?  Thanks.

     

     

  • 0 in reply to Peddler
    TI__Guru**** 159715 points

    Chris,

    If you do a build during a debug session CCS will detect that the program you are debugging has changed.  I don't have access to CCS at the moment but I believe the first time this happens it will prompt you if you want to reload the program and then after that it remembers your decision.  You can change this option.  I think it is Windows->Preferences.  Click on CCS and then Debug and there should be an option that says something about reloading the program automatically when it changes and it should have 3 settings; always, never and prompt (or something similar).

    Regards,

    John

     

  • 0 in reply to JohnS
    Intellectual 365 points

    Thanks, John.  I've searched for such an option but you've given me renewed hope.  I'll give it another try...

  • 0 in reply to Peddler
    TI__Guru**** 159715 points

    Here is the option:

  • 0 in reply to JohnS
    Intellectual 365 points

    Thanks, John,  This indeed provides some control of the behavior but it doesn't solve the main problems.  First, that when it reloads it typically creates a new, redundant tab for an existing file (ie, now there will be two tabs for the same file).  This can cause loss of data, especially when I don't realize there are two and make different edits to each one.  Secondly, when I do a debug it sometimes deletes one or both tabs so I have to go into the Projects view and re-load the .c file again. Third, when I simply try to do a build it does both a build and a full debug operation (time consuming). 

  • 0 in reply to Peddler
    TI__Guru**** 159715 points

    Chris,

    You have another thread discussing the tab issue.  Lets continue that thread.  

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/83649/288207.aspx#288207

    I will close this one off as the question posed here is answered.

    Regards,

    John