From: rebecca@bluestop.org
To: devel@edk2.groups.io, lersek@redhat.com,
ryszard.knop@linux.intel.com, michael.d.kinney@intel.com
Subject: Re: [edk2-devel] Adding DebugPkg to the main edk2 repo
Date: Tue, 7 May 2019 09:28:27 -0600 [thread overview]
Message-ID: <536f7e66-8232-30ef-e90c-057e89fdcc7e@bluestop.org> (raw)
In-Reply-To: <8354bb89-ce10-e45a-244b-5ae4c004b5e4@redhat.com>
On 2019-05-07 05:49, Laszlo Ersek wrote:
>
> I'd expect it to interoperate with any gdb server implementation.
>
> Whenever I use DebugPkg, to connect to a running QEMU instance, I launch the following gdb scriptlet (with "gdb -x") from a file:
>
> set height 0
> set architecture i386:x86-64:intel
> target remote localhost:1234
> source .../DebugPkg/Scripts/gdb_uefi.py
> reload-uefi -o .../Build/Ovmf3264/NOOPT_GCC48/X64/DebugPkg/GdbSyms/GdbSyms/DEBUG/GdbSyms.dll
Yup, I've documented the steps to use it at
https://code.bluestop.org/w/tianocore/debugging-with-gdb/ .
To work with modern versions of gdb which use Python 3, you can just run
2to3 (https://docs.python.org/3.7/library/2to3.html) on gdb_uefi.py
which I checked last night works.
I tried using it with a Bhyve build of OVMF
(https://github.com/freebsd/uefi-edk2/tree/bhyve/edk2-stable201903) but
it didn't work and I didn't have time to look into why. It might just be
because Bhyve's gdb server is fairly basic at the moment.
--
Rebecca Cran
prev parent reply other threads:[~2019-05-07 15:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-07 2:04 Adding DebugPkg to the main edk2 repo rebecca
2019-05-07 6:13 ` [edk2-devel] " Michael D Kinney
2019-05-07 8:59 ` Ryszard Knop
2019-05-07 11:49 ` Laszlo Ersek
2019-05-07 15:28 ` rebecca [this message]
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=536f7e66-8232-30ef-e90c-057e89fdcc7e@bluestop.org \
--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