From: Thomas Huth <thuth@redhat.com>
To: "mar.krzeminski" <mar.krzeminski@gmail.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>
Subject: Re: [Qemu-devel] Debugging u-boot after relocation on arm machie
Date: Thu, 8 Oct 2015 13:22:28 +0200 [thread overview]
Message-ID: <561651F4.5050804@redhat.com> (raw)
In-Reply-To: <5615653D.3000405@gmail.com>
On 07/10/15 20:32, mar.krzeminski wrote:
> 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.
Are you using software breakpoints or hardware breakpoints?
In case you're using software breakpoints, maybe they get clobbered by
the relocation / reloading?
Thomas
next prev parent reply other threads:[~2015-10-08 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 18:32 [Qemu-devel] Debugging u-boot after relocation on arm machie mar.krzeminski
2015-10-08 11:22 ` Thomas Huth [this message]
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=561651F4.5050804@redhat.com \
--to=thuth@redhat.com \
--cc=crosthwaitepeter@gmail.com \
--cc=mar.krzeminski@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).