Okay, well, I worked this out. But as always, there are still problems.
This is the tutorial that worked for me. Following this post I was able to index the kernel. Attempting to build the kernel in Eclipse still fails, but it really isn't a problem because it is just as easy to build the kernel on the command line. So there it is, a working, indexed kernel project.
From this point, I would like to integrate this process with KGDB debugging. The kernel that I have indexed is a KGDB enabled build that I know functions properly. Befor I started workng with eclipse, I was able to get KGDB debugging working to my satisfaction (see my previous posts if interested).
Now here comes the trouble. I want to attach eclipse CDT debugging to an active KGDB enabled kernel. When I use a .gdbinit file, none of the commands are interpreted correctly. Namely, if I have "target remote /dev/ttyS0" in the .gdbinit file, I get a "Project is not currently being run" error box. Yet, if I copy the exact same command into the console box within eclipse, no error occurs. This is really a shame because that kind of eliminates the benefits of the GUI.
Does anyone have experience with remote debugging within eclipse? I would just like to know what settings I should use for configuring the debugging dialogue. I'm pretty sure that I want to use just the gdb debugger, as opposed to the gdbserver debugger for attaching to a remote gdb stub. Other things like shared libraries continue to confound me. I really don't want to overload this post with information about my problems, so I'll try to limit the details, suffice to say that I have been working on this for a while now and would appreciate any help you guys can give me.
Thanks in advance!
|