From: "Boeuf, Sebastien" <sebastien.boeuf@intel.com>
To: "kraxel@redhat.com" <kraxel@redhat.com>,
"devel@edk2.groups.io" <devel@edk2.groups.io>
Cc: "Yao, Jiewen" <jiewen.yao@intel.com>
Subject: Re: [edk2-devel] Debug OVMF
Date: Mon, 9 May 2022 10:00:57 +0000 [thread overview]
Message-ID: <9db9a4e4993be2641c2e8752a456481cb71a1181.camel@intel.com> (raw)
In-Reply-To: <20220509094917.sydwsa6iy46eeroc@sirius.home.kraxel.org>
On Mon, 2022-05-09 at 11:49 +0200, kraxel@redhat.com wrote:
> On Mon, May 09, 2022 at 09:32:52AM +0000, Boeuf, Sebastien wrote:
> > Hi,
> >
> > I'm trying to debug OVMF with gdb connected to Cloud Hypervisor but
> > the
> > problem is that the debug binary that I have generated doesn't
> > contain
> > any symbols. Do you know how to generate debug symbols for OVMF?
>
> Build/OvmfX64/DEBUG_GCC5/X64/*.debug
>
> You might want checkout BaseTools/Scripts/efi_*.py too (didn't try
> them
> myself yet).
Ah thanks for the pointers, I'll try these :)
Sebastien
>
> take care,
> Gerd
>
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 5 208 026.16 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2022-05-09 10:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 9:32 Debug OVMF Boeuf, Sebastien
2022-05-09 9:49 ` [edk2-devel] " Gerd Hoffmann
2022-05-09 10:00 ` Boeuf, Sebastien [this message]
2022-05-09 18:18 ` Andrew Fish
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=9db9a4e4993be2641c2e8752a456481cb71a1181.camel@intel.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