From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, afish@apple.com
Subject: Re: [edk2-devel] OVMF gdb seems to require "stone knives and bearskins" to debug code?
Date: Mon, 25 May 2020 20:19:55 -0600 [thread overview]
Message-ID: <5ea5709b-aa92-84e5-463d-df4801635cd8@bsdio.com> (raw)
In-Reply-To: <50EEBF6E-8BB1-461D-B252-D37D2990957D@apple.com>
On 5/24/20 9:30 PM, Andrew Fish via groups.io wrote:
> I could open source an lldb symbolication Python script and I'm happy
> to explain the common logic to some one to make it easier to port this
> lldb command [3] to gdb. The command can load symbols for any address
> that is located in a loaded PE/COFF image, and when you import the
> command into lldb it symbolicates the current frame.
As Laszlo has already explained, information about debugging with gdb is
a bit scattered. I seem to recall there were discussion about getting
the DebugPkg into edk2, but there was disagreement about it.
However, since I work on platforms which have lldb in base (FreeBSD) or
are easily available (Linux), I'd certainly be interested if you were to
open source the efi_symolicate.py script and I could learn how to use lldb.
--
Rebecca Cran
next prev parent reply other threads:[~2020-05-26 2:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 3:30 OVMF gdb seems to require "stone knives and bearskins" to debug code? Andrew Fish
2020-05-25 19:15 ` [edk2-devel] " Laszlo Ersek
2020-05-25 23:14 ` Andrew Fish
2020-05-26 11:22 ` Laszlo Ersek
2020-05-26 2:19 ` Rebecca Cran [this message]
2020-05-26 3:11 ` Andrew Fish
2020-05-26 5:57 ` Andrei Warkentin
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=5ea5709b-aa92-84e5-463d-df4801635cd8@bsdio.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