From: Xuebing wang <xbing6@gmail.com>
To: Peter Maydell <peter.maydell@linaro.org>,
Jani Kokkonen <janimikokkonen@gmail.com>
Cc: Claudio Fontana <hw.claudio@gmail.com>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Debugging aarch64 guest running on Foundationv8 model
Date: Thu, 27 Feb 2014 21:21:43 +0800 [thread overview]
Message-ID: <530F3BE7.9060704@gmail.com> (raw)
In-Reply-To: <CAFEAcA9UTq7PxAb6nQ9Y7RU24t=-BJ3cfxf4mYM4ek8V-HHqUQ@mail.gmail.com>
Hi Jani,
Is below video similar to what you want? This video shows cross-debug
armv8 linux kernel (using armv8-gdb + armv8-qemu).
http://www.youtube.com/watch?v=MLu5EzheHIM
On 02/27/2014 05:52 PM, Peter Maydell wrote:
> On 27 February 2014 09:45, Jani Kokkonen <janimikokkonen@gmail.com> wrote:
>> Hi,
>>
>> I would like to debug a Qemu guest linux kernel under Foundationv8 model and
>> I tried the following setup:
>>
>> 1. Foundationv8 model started with --network=nat and
>> --network-nat-ports=1234=1234 options
>> 2. In Foundationv8 model I started qemu-system-aarch64 with the command
>> line:
>>
>> ./qemu-system-aarch64 -M virt -cpu host -kernel Image -serial stdio
>> -display none -enable-kvm -gdb tcp::1234 -S
>>
>> 3. I start debugging the guest kernel with aarch64-linux-gnu-gdb vmlinux
>> and with target remote:1234 command.
>>
>> However when I set any breakpoint I will get error message:
>> "Cannot insert breakpoint 1.
>> Error accessing memory address 0xffffffc000636498: Unknown error -1"
>> In addition stepi or any other run related command does not work.
> You would need to implement breakpoint support for AArch64 in
> both KVM and QEMU, I think. That feature is currently not implemented.
>
> thanks
> -- PMM
>
>
--
Thanks,
Xuebing Wang
next prev parent reply other threads:[~2014-02-27 13:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 9:45 [Qemu-devel] Debugging aarch64 guest running on Foundationv8 model Jani Kokkonen
2014-02-27 9:52 ` Peter Maydell
2014-02-27 13:21 ` Xuebing wang [this message]
2014-02-27 15:35 ` Jani Kokkonen
2014-02-28 1:29 ` Xuebing wang
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=530F3BE7.9060704@gmail.com \
--to=xbing6@gmail.com \
--cc=hw.claudio@gmail.com \
--cc=janimikokkonen@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).