From: "Pedro Falcato via groups.io" <pedro.falcato=gmail.com@groups.io>
To: Rebecca Cran <rebecca@bsdio.com>
Cc: devel@edk2.groups.io, Doug Flick <dougflick@microsoft.com>
Subject: Re: [edk2-devel] Debugging EFI Runtime crash when trying to update DBX for Secure Boot in Linux (fwupdmgr update)
Date: Mon, 2 Dec 2024 23:47:43 +0000 [thread overview]
Message-ID: <CAKbZUD2cHwFdaqmzMTOVR5EnikU49BYYJOh-nPyEASfOpgorwQ@mail.gmail.com> (raw)
In-Reply-To: <a87493df-20a7-4039-a3c9-f00a5e1b189a@bsdio.com>
On Mon, Dec 2, 2024 at 11:39 PM Rebecca Cran <rebecca@bsdio.com> wrote:
>
> On 12/2/24 4:29 PM, Pedro Falcato wrote:
>
> > On Mon, Dec 2, 2024 at 9:25 PM Rebecca Cran via groups.io
> > <rebecca=bsdio.com@groups.io> wrote:
> >>
> >> I have no idea how to go about debugging why the SetVariable call is
> >> causing the crash. Is it likely to be the way I've got dbxDefault set
> >> up, or does anyone know how I could debug it further?
> > Since this seems to be a dev board, don't you have the symbols for
> > your firmware? :)
>
> I do have symbols, but I assumed JTAG debugging code once the OS is
> running is a bit more complicated than in the DXE phase.
FWIW, I wasn't implying fancy debugging but rather something as simple
as getting the crash IP and symbolizing that (etc)
--
Pedro
-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#120858): https://edk2.groups.io/g/devel/message/120858
Mute This Topic: https://groups.io/mt/109889108/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-
next prev parent reply other threads:[~2024-12-02 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 21:25 [edk2-devel] Debugging EFI Runtime crash when trying to update DBX for Secure Boot in Linux (fwupdmgr update) Rebecca Cran
2024-12-02 23:29 ` Pedro Falcato via groups.io
2024-12-02 23:39 ` Rebecca Cran
2024-12-02 23:47 ` Pedro Falcato via groups.io [this message]
2024-12-03 9:13 ` Ard Biesheuvel via groups.io
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=CAKbZUD2cHwFdaqmzMTOVR5EnikU49BYYJOh-nPyEASfOpgorwQ@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