• State TI Thinks Resolved
  • Locked Locked
  • Replies 9 replies
  • Answers 1 answer
  • Subscribers 55 subscribers
  • Views 2701 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.

CCS: Enable C/C++ breakpoint (For GDB use)

Glu Nuts
Prodigy 10 points

Tool/software: Code Composer Studio

Hello everyone,

I am a new user of CCS and I use it to target various archs.

Sometimes, I build my code with GCC on x86 and use GDB to debug (Unitary test, for exemple). CCSv6 (Eclipse) is a good front end for GDB and it currently work like a charm.

But, I don't understand why -in the CCS Editor- I can only set CCS breakpoint (used by TI compiler and not recognized by GDB). :

Currently the workaround is easy : I use the integrated GDB console to set breakpoints.

Have you some ideas to enable it? This can be a .csproject instruction or a CCS capability disabled?

  • 0
    TI__Guru**** 429930 points
    Hello,
    If in a GDB debug session, CCS should default to Eclipse CDT breakpoints if the open source file is not associated with a CCS project. How did you open the source file? Did the debugger open it during debug?

    Thanks
    ki
  • 0 in reply to Ki
    Prodigy 40 points
    Hello,

    Thank you for your reply.

    All the source files seem to be in the CCS project. I open the source file by the Project Explorer in CSS and, during step to step debug, GDB open the files to follow the execution.

    The point I don't understand is why the CCS editor is unable to add C/C++ Breakpoint before I even start the debug.
  • 0 in reply to Etienne RABY
    TI__Guru**** 429930 points

    Etienne RABY said:
    All the source files seem to be in the CCS project

    In that case, the debugger will assume the CCS debugger is being used and will try using a CCS breakpoint

    Etienne RABY said:
    The point I don't understand is why the CCS editor is unable to add C/C++ Breakpoint before I even start the debug.

    It can. The issue is what debugger CCS assumes will be used. If the source files are in a CCS project, the it will assume the CCS debugger will be used and CCS breakpoints are required. If the source files were part of a standard Eclipse C makefile project, then it is assumed that GDB will be used and try setting a stand Eclipse C/C++ breakpoint. All of this is before a debug session is even started.

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    Ki-Soo Lee said:

    It can. The issue is what debugger CCS assumes will be used. If the source files are in a CCS project, the it will assume the CCS debugger will be used and CCS breakpoints are required. If the source files were part of a standard Eclipse C makefile project, then it is assumed that GDB will be used and try setting a stand Eclipse C/C++ breakpoint. All of this is before a debug session is even started.

    It makes sense but it is so sad... So the only way to use various compilators with CCS is to maintain two differents project file?

    There is no workaround to disable this "feature" and let me choose my breakpoint type?

    Anyway, thank you for your answers.

  • 0 in reply to Etienne RABY
    TI__Guru**** 429930 points

    Etienne RABY said:
    There is no workaround to disable this "feature" and let me choose my breakpoint type?

    You can choose for a standard C makefile project. But not for a CCS project.

    The reason this all behaves the way it does is due to prior feedback from customers. In the past, we supported the ability to set either breakpoints, regardless of debugger or project used. But a problem arose where customers using the CCS debugger would accidentally try using the standard Eclipse CDT breakpoint and then complain that breakpoints do not work with the CCS debugger. We tried to make this more clean by changing the wording to be more explicit and making the CCS breakpoint the default. But people still got crossed up. Since the vast majority of customers use CCS project for CCS debugging, we decided to just only provide the option for CCS breakpoints in those scenarios. Now we do have some customers who use (non-CCS) standard C makefile based projects with the CCS debugger. Hence we provide the option to toggle the option to use your non-CCS project to use CCS breakpoints. But we don't see very much customers going the other way (CCS projects with GDB).

    Hope this clears things up

    Thanks

    ki

  • 0 in reply to Ki
    Prodigy 40 points

    OK.

    Thanks you for your help.

  • 0 in reply to Etienne RABY
    Guru 37705 points

    I think this xkcd is appropriate here:

    https://xkcd.com/1172/

  • 0 in reply to Keith Barkley
    Prodigy 40 points
    Lol. Nice idea to by-pass a defective ctrl key, isn'it?

    Nonetheless, I don't think I'm a fool when I try to use an other compiler in my IDE. Qt Creator, Visual Studio, Eclipse and all others allow this without any problem. But I understand the CCS choice : forums are full of people who want to understand why their GDB breakpoints don't stop TI debugger.
  • 0 in reply to Etienne RABY
    Guru 37705 points
    I did not mean to imply that you were asking for anything foolish, just that anytime a developer makes a change - for whatever reason - some user depends on that previous feature in their workflow. They can't win. Microsoft can't even obsolete Paint!