All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ho Lee <flylist@linuxkernel.net>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] debugging relocated code
Date: Tue, 25 May 2004 11:49:00 -0700	[thread overview]
Message-ID: <01c501c44288$f1b25c00$1502a8c0@corp.skystream.com> (raw)
In-Reply-To: 001601c44286$0328e880$2900a8c0@foundation

Message
Hi Stuart,

Try the 'add-symbol-file' command. It relocates symbols to specified address.
In your case, you can relocate symbols by following commands.

    gdb> add-symbol-file u-boot 0x0ff03000
    gdb> file u-boot

You may find more information in gdb manual.

Sincerely,
Ho

----- Original Message -----
From: Stuart Yoder
To: u-boot-users at lists.sourceforge.net
Sent: Tuesday, May 25, 2004 11:27 AM
Subject: [U-Boot-Users] debugging relocated code


What is typically done to debug relocated code with gdb?   For example, u-boot is linked at 0xFFF0000, but then relocates itself to
0x0FF03000.   The debug symbols all reference the linked location.   After the relocation occurs gdb is lost as far as symbolic
information goes.

Am I supposed to link the code to the place I know it will end up after relocation?

Anyone know of a way in gdb to relocate all the symbols?

Thanks,

Stuart Yoder

  reply	other threads:[~2004-05-25 18:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-25 18:27 [U-Boot-Users] debugging relocated code Stuart Yoder
2004-05-25 18:49 ` Ho Lee [this message]
2004-05-25 19:26 ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2004-05-25 18:58 Kerl, John
2004-05-25 19:29 ` Wolfgang Denk
2004-05-25 19:35 Kerl, John
2004-05-25 21:47 ` Wolfgang Denk
2004-05-25 19:48 Woodruff, Richard
2004-05-25 19:55 Kerl, John
2004-05-25 20:08 Kerl, John
2004-05-25 21:54 ` Wolfgang Denk
2004-05-25 20:23 Rune Torgersen
2004-05-25 20:27 Kerl, John
2004-05-25 22:52 Alan J. Luse

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='01c501c44288$f1b25c00$1502a8c0@corp.skystream.com' \
    --to=flylist@linuxkernel.net \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.