> has someone experience how to use GDB to debug some code running at a
> different address than it was linked to? Note: GDB is connected via a JTAG
> tool to the target.

> I'm trying to debug some code linked to an address of my target's SDRAM area
> (0x30000000). But after reset a few hundred instructions are running at the
> address 0x00000000 instead, due to they are loaded from an external NAND
> memory into a CPU internal SRAM area at the beginning of its address space.
> I can step through all these assembler instructions, and after the code
> copies itself to the final address space gdb starts to display the source
> files and shows the lines where the CPU currently executes instructions
> from. I cannot change the linker script to link these reset relevant
> routines to the 0x00000000 address, because they are shared between the
> reset code and the high level code running at its final address area. It
> works, because everything calculates the addresses from offsets only
> (position independent code).

> Is there a way to tell GDB that the first hundred instructions are running
> from the real address at 0x00000000, but it should look for source file and
> line information as they where run from 0x30000000? Something like an
> address offset gdb should use to find the corresponding debug info in the
> local ELF iamge? I tried with the "section" command, but without success.
> Any (hidden) feature in gdb to do this?