From: "Liming Gao" <liming.gao@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"pedroyossis@gmail.com" <pedroyossis@gmail.com>
Subject: Re: [edk2-devel] Remove debug strings from OVMF.fd
Date: Wed, 17 Apr 2019 06:52:00 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14E42A041@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <CAJhsXKwgdALQR1LDmtXadujm_cXZ3WkB0SKHLBw6b1Ty1nkM+w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1001 bytes --]
<my-edk2-folder>/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Application/UiApp/UiApp/DEBUG/UiApp.dll is generated by GenFw tool. When GenFw tool convert ELF image to EFI image, it inserts the debug entry with the below string.
Thanks
Liming
From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of Pedro Barbosa
Sent: Tuesday, April 16, 2019 11:46 PM
To: devel@edk2.groups.io
Subject: [edk2-devel] Remove debug strings from OVMF.fd
Hi EDK2 developers,
I'm trying to build OVMF without debug symbols but even building as RELEASE, I still can see some strings on the PE files, such as:
<my-edk2-folder>/Build/OvmfX64/RELEASE_GCC5/X64/MdeModulePkg/Application/UiApp/UiApp/DEBUG/UiApp.dll
and many others in the format */DEBUG/*.dll
Is there a way to build without these strings?
Thanks!
--
[]s
Pedro Yóssis Silva Barbosa
Security Engineer, Google
PhD in Computer Science, UFCG, Brazil
sites.google.com/site/pedroysb<http://sites.google.com/site/pedroysb>
[-- Attachment #2: Type: text/html, Size: 5619 bytes --]
next prev parent reply other threads:[~2019-04-17 6:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 15:46 Remove debug strings from OVMF.fd Pedro Barbosa
2019-04-16 16:39 ` [edk2-devel] " Laszlo Ersek
2019-04-16 16:52 ` Andrew Fish
2019-04-17 6:52 ` Liming Gao [this message]
2019-04-17 17:35 ` Andrew Fish
2019-04-18 0:14 ` Liming Gao
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=4A89E2EF3DFEDB4C8BFDE51014F606A14E42A041@SHSMSX104.ccr.corp.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