After building the LTIB image, GDB version 6.6 is pulled into the image.  We are using the CodeSourcery toolchain:

arm-none-linux-gnueabi-gcc (Sourcery CodeBench Lite 2011.09-70) 4.6.1

When running GDB at the command line, it was not able to find the debug symbols that were actually present in our files.

As an attempt at fixing this, I downloaded the latest GDB from the GNU website.  This is version 7.10.1.

After cross building this and installing onto the target manually, GDB was now able to see the debug symbols and I was able to debug at the command line.

I noticed in the LTIB script for the build of GDB ver 6.6, that it patches the GDB source code with a patch related to the toolchain.  In my own build, I did absolutely no patching of the GDB source.

Why is this patch necessary? GDB seems to run fine without it.  Can we keep running this way and not expect further problems? Is there a known fix to make GDB version 6.6 run correctly?  Are the problems I saw with GDB ver 6.6 related to an issue of LogicPD upgrading the toolchain without ever going back and testing GDB with that new toolchain?

Thanks,

Jay