• Locked Locked
  • Replies 4 replies
  • Subscribers 56 subscribers
  • Views 736 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.

Linux CCS v5.1.0.07001 GDB debug issues...

Joe Cossette
Intellectual 780 points


Looks like there may be another issue in regards to GDB debugging.  None of the breakpoints seem to work in GDB debugging.  It goes thru the motions and sets them and adds them to the Breakpoints dialog, but whenever I resume it never hits any breakpoints and my program just runs to completion.

 

The only breakpoint which seems to work is the checkbox to “Stop on startup at: main”.

 

Also, "Assembly Step Into" and "Assembly Step Over" aren't working, they're greyed out.

 

Any suggestions?

 

  • TI__Guru**** 171309 points

    Joe,

    For the breakpoints, can you make sure they are setting the correct ones? Check:

    http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/p/100988/354274.aspx#354274

    The assembly step functionality is completely dependent on the GDB capabilities, therefore Eclipse will follow whatever is supported by the version you are using. Although I have seen on the internet that GDB is able to perform assembly step, I found no references of these commands being used by Eclipse when the project has source files written in C(only in assembly source code).

    I will keep investigating this, but so far it does not look promising.

    Regards,

    Rafael

  • in reply to desouza
    Intellectual 780 points

     

    I followed the link you have above, but when I look on the Breakpoint types menu there is no C/C++ Breakpoints as you mention, only Code Composer Studio Breakpoint.

    I appreciate your attempt at help.  At this point I am extremely frustrated, being an "early adopter" is giving me a stomach ulser...;(...

    I been working a bit with Patrick and Ray, and haven't yet heard back from them on my latest reply.  But I suspect some of these issues perhaps stem from the unorthodox way I may be using CCS/Eclipse.  I'll include here some of the info that may perhaps be helpful to others.  I suppose it's possible, but it doesn't seem probable that I'm the only one having issues like this.  Patrick asked me what type project I was using, and my reply is below:

    I’m not using a “project” at all.   I can’t because we’ve got our own Linux build environment and even if I try to use a makefile project it still does not build or work.

    So all I’m using is a debug configuration.  I’ve created a GDB debug configuration for remote debugging of ARM targets (we’re using TI 8148EVM).  Everything appears to be set up correctly.  I’ve configured it to use the Code Sourcery ARM GDB executable, and there’s a remote ARM GDB server running on the target.  I load the GDB server on the target and then run my GDB Debug config and it stops at main() (I checked the box in the debug config).  That’s the only breakpoint that appears to work.  If I double click on next source code line it appears to set a breakpoint (it adds the little mark on the source line and also adds it to the Breakpoint dialog), but when I run it it doesn’t stop at the breakpoint.

    Patrick asked me to also set the breakpoint type in the editor window, but the editor window I've got doesn't have any options in it to set the breakpoint type...I suppose it's an artifact of not having a project.  I've never used Eclipse before, and to me (coming from using commercial products like MSVC) it seems to have a number of redundant steps. If you're not actually building your code in the IDE for whatever reason (in my case I find I'm unable to integrate our internal Linux build environment into CCS/Eclipse), and if a debug configuration can be created without a project, and also run without a project, then you shouldn't need a project.  You (CCS developers) already know what type of debugger is being used from the debug configuration, why should I have to "set" the breakpoint type (and in this case I can't because those options aren't even available)?

    I think the way I'm using CCS/Eclipse is valid, that is to say, if I can't build in it I should still be able to debug in it.

    Admittedly, these are usability issues.  But as a developer I've got enough issues to deal with on a daily basis...I don't need an IDE giving me more problems...;(...



     

     

  • in reply to Joe Cossette
    TI__Genius 16520 points

    We were able to workaround the breakpoint issue by creating a dummy project and then linked the source files into the project. The problem is originated from the gdb debug session, where it opens a non-CEditor when the stackframe is selected. Futhermore, gdb breakpoint can only be set in the CEditor due to restructions in the standard ECLIPSE/CDT code base.

    I am trying to reproduce this issue by creating a host exe and debug with a gdb session, but without luck. Joe, it will be very useful if you can provide an example that duplicates your enviroment (i.e an exe). This can help me to submit a bug entry against Eclipse/CDT and provides the patch to fix this issue.

    Regards,
    Patrick

  • in reply to Patrick Chuong
    Prodigy 40 points

    Dear all,

    can somebody tell if this issue has been solved meanwhile? I'm facing the same issue with a C/C++ project and CCS 6.1used for unit-tests which I can't debug properly,  as no breakpoints can be set (missing option C/C++ breakpoint type) - but stepping trough works.

    Thanks for any news on this topic.

    Regards,

    Roland