![]() ![]() Previously installed command line debugging tools as described in a prior blogs entry of mine. Previously installed command line cross compilation tools as described in a prior blogs entry of mine. Knowledge on how to use Eclipse as an Integrated Development Environment (IDE) including the integrated debugger. ![]() A plain vanilla install for C & C++ has everything needed on the Eclipse side. ![]() Have extra software installed won’t hurt (I think) but it is not needed. You do not need any extra software plugins from Eclipse. Have Eclipse Neon for C & C++ development installed and available for use. Also, just to be clear, Eclipse is a moving target, the menu’s change between versions somewhat and what works in one version may be slightly different in another version. I think I was close in last week’s attempts, but was missing several minor, yet critical steps, so I never got it working. I’m happy to give credit to Michael Welling and Michael Casadevall for a fantastic amount of work getting remote debugging to work within Eclipse. ![]() The good news is that two people jumped in to help me with Eclipse. In my last blog I showed how to get command line remote gdb debugging working, and I was also able to get remote source code debugging working with the gui ddd and gdb. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |