• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 52 subscribers
  • Views 1496 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: single step disassembly - stop referencing C file between steps

Robert Wolfe
Mastermind 7860 points

Tool/software: Code Composer Studio

Hello,

When single stepping through disassembly, Ctrl-Shift-F5, after each step, it keeps going back to the associated C source file line.  Is there any way to stop that, i.e. just stick in the disassembly window.  I assume one of the Preferences, but I haven't been able to find it yet.

Thanks,

Robert

  • 0
    TI__Guru**** 464711 points
    Hi Robert,
    It is not possible to explicitly disable the source code correlation. As you noticed, every time you step, it will update the source file. If you close the source file, it will reopen it again and refresh it. Is there any particular reason why you wish to avoid this behavior?

    Thanks
    ki
  • 0 in reply to Ki
    Mastermind 7860 points

    Ki-Soo Lee said:
    Hi Robert,

    Is there any particular reason why you wish to avoid this behavior?

    Twice the work, or more.  Instead of rapid fire

    step, step, step, step, ...

    it's

    step, refocus to disassembly window, step, refocus to disassembly window, ...

    Thanks,

    Robert

  • 0 in reply to Robert Wolfe
    Mastermind 7860 points

    As follow-up, even when there is no source available, stepping takes the focus back to the top of the routine.  Again, instead of:

    step, step, step, step

    it's 

    step, refocus to stepped lines, step, refocus to stepped lines

    I've attached a picture of stepping through a division routine (without C source), with first image the step point, and the second image where I end up after the step has been executed

    Surprised, given the productivity impact, these issues were not more known, raised.  It's not the behavior of pre-Eclipse CCS (or most other IDE debugging tools I've used).

    Regards,

    Robert

  • 0 in reply to Robert Wolfe
    TI__Guru**** 464711 points

    The performance impact of single asm stepping appears fairly responsive to me, despite the focus issue... though I am working with pretty small projects.

    Yes, the disassembly window will refocus when you step into a function or loop. I don't think you can disable that "feature" either. If you are exclusively asm stepping, one workaround is to remove the loaded symbols (Run -> Load -> Remove All Symbols). This will eliminate all the refocus issues and make asm stepping more responsive. But you would lose source level debug visibility until you reload the symbols again.

    Thanks
    ki

  • 0 in reply to Ki
    Mastermind 7860 points

    Ki-Soo Lee said:

    The performance impact of single asm stepping appears fairly responsive to me, despite the focus issue... though I am working with pretty small projects. 

    Yes, the disassembly window will refocus when you step into a function or loop. I don't think you can disable that "feature" either. If you are exclusively asm stepping, one workaround is to remove the loaded symbols (Run -> Load -> Remove All Symbols). This will eliminate all the refocus issues and make asm stepping more responsive. But you would lose source level debug visibility until you reload the symbols again.

    Yes, and some cases, if I'm doing a lot of assembly debugging, it's a standalone, assembly-only module, exclusive like you said, so this disable approach could be used. But that's not always the case.  I'd suggest an option be added to stop the refocusing, for the case where the disassembly needs to be tied to the source level debug.  The source is already interspersed in the disassembly window ... no need to keep referencing back to it in another window after each step.  

    Thanks,

    Robert