From: "mar.krzeminski" <mar.krzeminski@gmail.com>
To: "qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>
Subject: [Qemu-devel] Debugging u-boot after relocation on arm machie
Date: Wed, 7 Oct 2015 20:32:29 +0200 [thread overview]
Message-ID: <5615653D.3000405@gmail.com> (raw)
Hello,
I am working on u-boot under qemu. Debugging before u-boots relocate
itself works just fine.
After relocation and reloading elf in gdb, qemu does no stop on breakpoint.
Generally I follow this instruction:
http://www.denx.de/wiki/view/DULG/DebuggingUBoot
I am debuging under eclipse - I'll test with clean gdb to be sure. As I
see some topics in this list,
there is some work ongoing regarding self-modyfying code on arm and gdb
stub.
Does someone tries to debug such applications?
Regards,
Marcin
next reply other threads:[~2015-10-07 18:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 18:32 mar.krzeminski [this message]
2015-10-08 11:22 ` [Qemu-devel] Debugging u-boot after relocation on arm machie Thomas Huth
2015-10-08 12:24 ` Marcin Krzemiński
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=5615653D.3000405@gmail.com \
--to=mar.krzeminski@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).