From: "Gao, Liming" <liming.gao@intel.com>
To: Matthijs Lavrijsen <mattiwatti@gmail.com>
Cc: "edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
"Yao, Jiewen" <jiewen.yao@intel.com>,
wang xiaofeng <winggundum82@163.com>
Subject: Re: latest basetools build pdb cannot be load by IDA6.95
Date: Tue, 22 Aug 2017 05:51:18 +0000 [thread overview]
Message-ID: <4A89E2EF3DFEDB4C8BFDE51014F606A14D774061@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <CAKJDwgX+-0iA-0cgTPdd+SBVgchLQ+fB-G4m86mQ-pq+sKhKVQ@mail.gmail.com>
Matthijs:
Thanks for your detail explanation. I will send this patch to keep GUID and DWORD in RSDS entry.
Thanks
Liming
>-----Original Message-----
>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
>Matthijs Lavrijsen
>Sent: Tuesday, August 22, 2017 12:33 PM
>To: Gao, Liming <liming.gao@intel.com>
>Cc: edk2-devel@lists.01.org; Yao, Jiewen <jiewen.yao@intel.com>; wang
>xiaofeng <winggundum82@163.com>
>Subject: Re: [edk2] latest basetools build pdb cannot be load by IDA6.95
>
>I just compiled GenFw to verify this, and the issue is indeed caused by
>e4129b0e5897d76885170bec9da996b266f185f9.
>
>The problem is not with zeroing debug directories than the CodeView one,
>but setting the 'unknown' fields of the RSDS entry to zero. These fields
>are actually a GUID and DWORD respectively: the GUID identifies the PDB to
>make it possible to verify that a given PDB matches the PE file, and the
>DWORD is the "age" of the PDB which is simply a helper value that is
>incremented by 1 by the linker every time the file is remade. Wiping the
>GUID will cause PDB parsers (such as the MS DIA SDK that IDA and most other
>tools use) to treat the PDB as a mismatch and refuse to load it.
>
>W.r.t. zeroing the unwanted debug directories that were added in VS2015:
>there is actually a better solution for this than plain wiping for one of
>the two. It is possible to exclude IMAGE_DEBUG_TYPE_ILTCG (= 14) through
>the undocumented linker flag /NOCOFFGRPINFO. This means the space is
>saved
>even in uncompressed images. I'm not aware of any such solution for
>IMAGE_DEBUG_TYPE_POGO (= 13) however, so that will still have to be
>zeroed.
>
>On Tue, Aug 22, 2017 at 5:14 AM, Gao, Liming <liming.gao@intel.com> wrote:
>
>> Xiaofeng:
>> Could you help verify the change in GenFw tool?
>>
>> You can refer to https://github.com/tianocore/tianocore.github.io/wiki/
>> Windows-systems Compile Tools section to compile GenFw tool, and try it.
>>
>> Thanks
>> Liming
>> From: wang xiaofeng [mailto:winggundum82@163.com]
>> Sent: Tuesday, August 22, 2017 9:12 AM
>> To: wang xiaofeng <winggundum82@163.com>
>> Cc: Yao, Jiewen <jiewen.yao@intel.com>; Gao, Liming
><liming.gao@intel.com>;
>> edk2-devel@lists.01.org
>> Subject: Re:Re:Re: [edk2] latest basetools build pdb cannot be load by
>> IDA6.95
>>
>> Liming,
>> Do you think we should roll back the change? I am not sure whether
>> any source level debug tool will have the same issue with pdb information
>> change.
>>
>>
>>
>>
>> 在 2017-08-21 17:33:30,"wang xiaofeng"
><winggundum82@163.com<mailto:w
>> inggundum82@163.com>> 写道:
>>
>> Liming,
>> It should be the change that lead to IDA cannot load pdb. I just roll
>> back to previous GENFW and IDA can load pdb file now.
>>
>>
>>
>>
>>
>>
>> At 2017-08-21 16:29:55, "Yao, Jiewen" <jiewen.yao@intel.com<mailto:j
>> iewen.yao@intel.com>> wrote:
>>
>> >FYI: here is IDA https://www.hex-rays.com/products/ida/overview.shtml
>>
>> >
>>
>> >Thank you
>>
>> >Yao Jiewen
>>
>> >
>>
>> >
>>
>> >From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org<mailto:edk2-
>> devel-bounces@lists.01.org>] On Behalf Of Gao, Liming
>>
>> >Sent: Monday, August 21, 2017 4:17 PM
>>
>> >To: wang xiaofeng
><winggundum82@163.com<mailto:winggundum82@163.com>>;
>> edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
>>
>> >Subject: Re: [edk2] latest basetools build pdb cannot be load by IDA6.95
>>
>> >
>>
>> >Xiaofeng:
>>
>> > What is IDA? What message is required by it?
>>
>> >
>>
>> > Recently, I make the change in BaseTools to clear the unused field in
>> DebugEntry to zero. It may impact IDA. Here is the change. Could you help
>> identify whether this change cause IDA load issue?
>>
>> >
>>
>> >SHA-1: e4129b0e5897d76885170bec9da996b266f185f9
>>
>> >
>>
>> >* BaseTools: Update GenFw to clear unused debug entry generated by VS
>> tool chain
>>
>> >
>>
>> >https://bugzilla.tianocore.org/show_bug.cgi?id=600
>>
>> >
>>
>> >Contributed-under: TianoCore Contribution Agreement 1.0
>>
>> >Signed-off-by: Liming Gao <liming.gao@intel.com<mailto:l
>> iming.gao@intel.com><mailto:liming.gao@intel.com<mailto:limi
>> ng.gao@intel.com>>>
>>
>> >Reviewed-by: Yonghong Zhu <yonghong.zhu@intel.com<mailto:
>> yonghong.zhu@intel.com><mailto:yonghong.zhu@intel.com<mailto:
>> yonghong.zhu@intel.com>>>
>>
>> >
>>
>> >Thanks
>>
>> >Liming
>>
>> >>-----Original Message-----
>>
>> >>From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org<mailto:edk2-
>> devel-bounces@lists.01.org>] On Behalf Of
>>
>> >>wang xiaofeng
>>
>> >>Sent: Monday, August 21, 2017 2:27 PM
>>
>> >>To: edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org><mailto:
>> edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>>
>>
>> >>Subject: [edk2] latest basetools build pdb cannot be load by IDA6.95
>>
>> >>
>>
>> >>Hi Basetool owners,
>>
>> >> I updated basetool to svn24984 (edk2 mirror )or even latest svn,
>> after
>>
>> >>build all the x64 efi files fail to load pdb by IDA6.95. It used to work
>> with
>>
>> >>svn23946 revision(near Feb 2017).
>>
>> >> Any change may related to this issue?
>>
>> >> I have reported bugs to IDA . But since this is a regression
>> issue of
>>
>> >>basetools ,it will be helpful that basetools can also help to debug this
>> issue.
>>
>> >>_______________________________________________
>>
>> >>edk2-devel mailing list
>>
>> >>edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org><mailto:
>> edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>>
>>
>> >>https://lists.01.org/mailman/listinfo/edk2-devel
>>
>> >_______________________________________________
>>
>> >edk2-devel mailing list
>>
>> >edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org><mailto:
>> edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>>
>>
>> >https://lists.01.org/mailman/listinfo/edk2-devel
>>
>> >_______________________________________________
>>
>> >edk2-devel mailing list
>>
>> >edk2-devel@lists.01.org<mailto:edk2-devel@lists.01.org>
>>
>> >https://lists.01.org/mailman/listinfo/edk2-devel
>>
>>
>>
>>
>> 【网易自营|30天无忧退货】不到同款1折价!Tory Burch制造商美式休
>闲人字拖限时仅29.9元>><http
>> ://you.163.com/item/detail?id=1185012&from=web_gg_mail_jiaobiao_9>
>> _______________________________________________
>> edk2-devel mailing list
>> edk2-devel@lists.01.org
>> https://lists.01.org/mailman/listinfo/edk2-devel
>>
>_______________________________________________
>edk2-devel mailing list
>edk2-devel@lists.01.org
>https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2017-08-22 5:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 6:26 latest basetools build pdb cannot be load by IDA6.95 wang xiaofeng
2017-08-21 8:17 ` Gao, Liming
2017-08-21 8:29 ` Yao, Jiewen
2017-08-21 9:33 ` wang xiaofeng
2017-08-22 1:12 ` wang xiaofeng
2017-08-22 3:14 ` Gao, Liming
2017-08-22 4:33 ` Matthijs Lavrijsen
2017-08-22 5:51 ` Gao, Liming [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=4A89E2EF3DFEDB4C8BFDE51014F606A14D774061@shsmsx102.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