As a follow on, I rebuilt the native gdb from 6.8 sources
thus:

# ./configure
# make
# make install

It correctly interprets the arm elf file debug information,
i.e. it's able to find symbols in source files via the
"list" command etc.
Why is the simple act of cross-targeting gdb destroying this
capability?


R.

----- Original Message ----
From: Robert Trask <rt_traskyahoo.com>
To: gdbsources.redhat.com
Sent: Tuesday, May 13, 2008 7:08:22 PM
Subject: How to build & run ARM gdb?

Hello,
I am doing remote ARM system development cross hosted on a
Redhat FC4 machine.
For building gdb I do the following:

# ./configure --target=arm-none-eabi
# make

The
resulting gdb seems to work ok vis-a-vis connecting to the
target via
the remote protocol but it has problems interpreting the
debug info in
the executable thus:

(gdb) list  <symbol_name>
No line number known for <symbol_name>.

Apparently this gdb can't understand the elf file?

But, the gdb that came with the RH distribution, ( GNU gdb
Red Hat Linux (6.3.0.0-1.21rh)  DOES understand the elf file
and correctly finds the <symbol_name> in the
appropriate source file.
Of course, since it was configured for
"i386-redhat-linux-gnu" it has no hope of properly
interacting with the remote ARM target.

I have tried all manner of different configurations (all
accepted by config.sub). I get the same result.

What is happening here and how do I fix it?
I have tried this with gdb 6.7.1 and 6.8. I am using Redhat
Fedore Core 4.

R.