From: Ard Biesheuvel <ard.biesheuvel@linaro.org>
To: Laszlo Ersek <lersek@redhat.com>
Cc: "Tian, Feng" <feng.tian@intel.com>,
edk2-devel-01 <edk2-devel@ml01.01.org>,
Leif Lindholm <leif.lindholm@linaro.org>,
"Gao, Liming" <liming.gao@intel.com>,
"Kinney, Michael D" <michael.d.kinney@intel.com>
Subject: Re: DxeCore assert during initialization
Date: Thu, 23 Feb 2017 17:38:25 +0000 [thread overview]
Message-ID: <CAKv+Gu8nMcZsPjXhvjrDeOp+RyCh6GFR-t49H6AqAvSWgxeqXg@mail.gmail.com> (raw)
In-Reply-To: <d31602d0-a776-0fe5-8429-b94c960189bf@redhat.com>
On 23 February 2017 at 17:33, Laszlo Ersek <lersek@redhat.com> wrote:
> On 02/23/17 18:29, Laszlo Ersek wrote:
>
>> This is with ArmVirtQemu @ c5c9e7e298ed, running on QEMU v2.8.0-1290-gc3618551719b, using TCG.
>
> Hm, I have some patches in QEMU, so that hash will likely not resolve on
> your side. The first upstream ancestor is e295a154c2a9.
>
Could you please double check?
$ git show e295a154c2a9
fatal: ambiguous argument 'e295a154c2a9': unknown revision or path not
in the working tree.
In any case, it faults on address 0x1383C6E94 with a data abort due to
permissions, which can only be caused by a store to read-only region.
This is at the end of the .text segment of UiApp.dll
Could you open the .dll in GDB (you may need to do 'set architecture
aarch64'), and paste the output of
disas *0x3070
?
Thanks
next prev parent reply other threads:[~2017-02-23 17:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 17:16 DxeCore assert during initialization Marcin Wojtas
2017-02-23 17:17 ` Ard Biesheuvel
2017-02-23 17:29 ` Laszlo Ersek
2017-02-23 17:33 ` Laszlo Ersek
2017-02-23 17:38 ` Ard Biesheuvel [this message]
2017-02-23 17:51 ` Laszlo Ersek
2017-02-23 17:55 ` Ard Biesheuvel
2017-02-23 17:34 ` Marcin Wojtas
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-list 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=CAKv+Gu8nMcZsPjXhvjrDeOp+RyCh6GFR-t49H6AqAvSWgxeqXg@mail.gmail.com \
--to=devel@edk2.groups.io \
/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