From mboxrd@z Thu Jan  1 00:00:00 1970
From: Vladimir Gurevich <vag@paulidav.org>
Date: Wed, 05 Feb 2003 17:16:28 -0800
Subject: [U-Boot-Users] Debugging U-boot after relocation
Message-ID: <3E41B76C.8060207@paulidav.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Hello,

I am trying to debug U-boot after the code has been relocated and
I got some problems. Maybe I don't know gdb well enough...
BTW, I use ELDK tools and BDI-2000 on PPC405GP-based board.

I can debug U-boot before the relocation step easily. So I
put a breakpoint at the "blr" instruction that preceeds the
"in_ram" label. After it occurs, I issue the following gdb
commands:

(gdb) info line *(&in_ram)
Line 1310 of "/home/vgurevic/vag/u-boot-0.2.0/cpu/ppc4xx/start.S"
starts at address 0xfffc25a8 <in_ram> and ends at 0xfffc25ac <in_ram+4>.
(gdb) file

(gdb) add-symbol-file u-boot 0x7fd0000  <- That's the reloc. addr
(gdb) target remote bdi:2001

(gdb) info line *(&in_ram)
Line 510 of "/home/vgurevic/vag/u-boot-0.2.0/cpu/ppc4xx/start.S"
starts@address 0x7fd26e8 <ext_bus_cntlr_init> and ends at 0xfffc0100.
                                                             ^^^^^^^^^^^

So that's where the isue is: gdb can't interpret line numbers
correctly anymore and can't show (via ddd or emacs interface)
where you are. It is still possible to step through the code
using "stepi" but not much more.

Does anyone know how to deal with this issue or maybe there is
a totally different way to debug U-boot?

Thanks,
Vladimir