I know this is kind of an old thread, but I thought I might raise the subject
again:
I've found a way to get the desired binary (with the pdbfile erased from the
PE/COFF header) with the current GenFw implementation by dividing the operation
into 2 phases:
1. Erase the pdb header with -z --><file_without_pdb>.tmp_bin
2. Generate the efi rom with -e from < file_without_pdb>.tmp_bin
--><target>.efi
I've done so in my Conf/build_rules.txt file and got the desired rom with its
header clean of any pdb file:
"$(GENFW)" -z -o ${dst} ${src} $(GENFW_FLAGS)
"$(GENFW)" -e $(MODULE_TYPE) -o ${dst} ${dst} $(GENFW_FLAGS)
My question is - is my procedure correct? Is the output file an healthy PE/COFF
file?
Thanks,
Ari
From: Yossef Efraim [mailto:yoss...@mellanox.com]
Sent: Wednesday, December 26, 2012 4:25 PM
To: edk2-devel@lists.sourceforge.net
Subject: Re: [edk2] PdbFileName
Thanks liming,
I really appreciate your (and the rest of guys here ) help !
Enjoy the holidays ( whoever is having them).
Yossef
From: Gao, Liming [mailto:liming....@intel.com]
Sent: Wednesday, December 26, 2012 3:47 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] PdbFileName
Yossefe:
For GCC tool chain, the compiled image is ELF image, which will be converted
to PE image by GenFw. But, GenFw will always append DEBUG entry for it, because
GenFw tool has no knowledge to know whether it is RELEASE or DEBUG image. So,
you will also see PDB file for release image.
Jordan proposes to use -z option of GenFw to zero DEBUG entry for release
image, then you don't see PDB file path. But now, GenFw tool doesn't support -z
and -e option to be used together. I think that this is an issue in GenFw. We
will fix it.
Thanks
Liming
From: Yossef Efraim
[mailto:yoss...@mellanox.com]<mailto:[mailto:yoss...@mellanox.com]>
Sent: Tuesday, December 25, 2012 8:08 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] PdbFileName
I'm using GCC44 , X64 arch ( edk2 in installed on red hat enterprise linux ).
I do not see the RELEASE target compiler for GCC44.
Thanks
Yossef
From: Gao, Liming [mailto:liming....@intel.com]
Sent: Tuesday, December 25, 2012 10:53 AM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] PdbFileName
RELEASE target is to use the different compiler options, which doesn't auto
inhibits DMDEPKG_NDEBUG' definition. You can find RELEASE target compiler in
Conf\tools_def.txt file.
Could you show your steps on RELEASE target with PDB file name? Which tool
chain and which platform is used by you?
Besides, I just try NT32 with RELEASE build and VS2008x86 tool chain, and enter
into Shell, type DH with ImageHandle. No PDB file path is shown.
Thanks
Liming
From: Yossef Efraim
[mailto:yoss...@mellanox.com]<mailto:[mailto:yoss...@mellanox.com]>
Sent: Tuesday, December 25, 2012 4:42 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] PdbFileName
Thank you Liming.
But I see it for both builds ( made sure the 'RELEASE' image was used ), seems
like RELEASE doesn't inhibits the 'DMDEPKG_NDEBUG' definition.
IMO it is related to the debug symbols thread Ben Schroder opened.
From: Gao, Liming [mailto:liming....@intel.com]
Sent: Tuesday, December 25, 2012 6:49 AM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: Re: [edk2] PdbFileName
When RELEASE build, there is no PDB file. Please make sure RELEASE image is
used.
Thanks
Liming
From: Yossef Efraim
[mailto:yoss...@mellanox.com]<mailto:[mailto:yoss...@mellanox.com]>
Sent: Monday, December 24, 2012 10:53 PM
To: edk2-devel@lists.sourceforge.net<mailto:edk2-devel@lists.sourceforge.net>
Subject: [edk2] PdbFileName
Hi,
When I 'dh' my image handle in the uefi shell, I see the PdbFileName ( <full
path>.<DriverSample.dll> ). I see it both for RELAESE & DEBUG builds.
How can I eliminate this from appearing ?
Thanks,
Yossef
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk
_______________________________________________
edk2-devel mailing list
edk2-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/edk2-devel
