From: "Palmer, Thomas" <thomas.palmer@hpe.com>
To: Laszlo Ersek <lersek@redhat.com>,
Johannes Swoboda <johannes.swoboda@student.tuwien.ac.at>
Cc: Michael Kinney <michael.d.kinney@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"clemens.hlauschek@inso.tuwien.ac.at"
<clemens.hlauschek@inso.tuwien.ac.at>
Subject: Re: Source code debugging of OVMF
Date: Mon, 16 Apr 2018 16:53:20 +0000 [thread overview]
Message-ID: <TU4PR8401MB1086A3311EA9A4BA0B28F2AFEDB00@TU4PR8401MB1086.NAMPRD84.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <12fe2332-c864-60e1-4f12-280e9939449f@redhat.com>
I use Andrew WIP's stuff often as well. Just put the GdbSyms.inf in your DSC (not FDF) and build. My .gdbinit script looks like this:
set architecture i386:x86-64:intel
target remote localhost:1234
source DebugPkg/Scripts/gdb_uefi.py
reload-uefi -o Build/OvmfX64/DEBUG_GCC5/X64/DebugPkg/GdbSyms/GdbSyms/DEBUG/GdbSyms.dll
Andrew, I owe you a couple of beers if we ever meet.
Regards,
Thomas Palmer
"I have only made this letter longer because I have not had the time to make it shorter" - Blaise Pascal
-----Original Message-----
From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of Laszlo Ersek
Sent: Monday, April 16, 2018 11:14 AM
To: Johannes Swoboda <johannes.swoboda@student.tuwien.ac.at>
Cc: Michael Kinney <michael.d.kinney@intel.com>; edk2-devel@lists.01.org; clemens.hlauschek@inso.tuwien.ac.at
Subject: Re: [edk2] Source code debugging of OVMF
Hi Johannes,
On 04/16/18 13:09, Johannes Swoboda wrote:
> How are you ovmf developer debugging it?
In general I add DEBUG statements, grep the tree for protocol / PPI GUIDs, and use an editor with good ctags support.
Here's another thread that you might find useful:
http://edk2-devel.narkive.com/6BRVus92/qestion-about-how-to-debug-ovmf-on-qemu
Occasionally I do use gdb with QEMU, but the solution I use is not suitable for debugging modules in the SEC and PEI phases, only in DXE. I have some terribly rough patches in my local tree that are based on <https://github.com/andreiw/andreiw-wip/tree/master/uefi/DebugPkg>.
I don't recall having any luck with SOURCE_DEBUG_ENABLE and the UDK debugger <https://firmware.intel.com/develop/intel-uefi-tools-and-utilities/intel-uefi-development-kit-debugger-tool>,
but admittedly it's been a while (= years?) since I last tried to connect debugger VM with debugge VM over a virtual serial port. Others have more recently confirmed it works for them. I think Mike uses it successfully, from a Windows debugger machine maybe?
Thanks,
Laszlo
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.01.org
https://lists.01.org/mailman/listinfo/edk2-devel
next prev parent reply other threads:[~2018-04-16 16:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 11:09 Source code debugging of OVMF Johannes Swoboda
2018-04-16 15:26 ` Richardson, Brian
2018-04-16 16:03 ` Blibbet
2018-04-20 13:32 ` Johannes Swoboda
2018-04-16 16:13 ` Laszlo Ersek
2018-04-16 16:53 ` Palmer, Thomas [this message]
2018-04-16 18:25 ` Rebecca Cran
2018-04-16 19:57 ` Laszlo Ersek
2018-04-19 2:46 ` Rebecca Cran
2018-04-19 8:41 ` Laszlo Ersek
2018-04-20 14:54 ` gdb reload-uefi missing EFI_SYSTEM_TABLE_POINTER [was: Source code debugging of OVMF] Johannes Swoboda
2018-04-20 15:20 ` Laszlo Ersek
2018-04-20 15:58 ` Palmer, Thomas
2018-04-20 16:38 ` Johannes Swoboda
2018-04-20 16:45 ` Palmer, Thomas
2018-04-20 16:49 ` Rebecca Cran
2018-04-24 2:13 ` Gary Lin
2018-05-24 12:52 ` Johannes Swoboda
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=TU4PR8401MB1086A3311EA9A4BA0B28F2AFEDB00@TU4PR8401MB1086.NAMPRD84.PROD.OUTLOOK.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