From: "Carsey, Jaben" <jaben.carsey@intel.com>
To: "Zhu, Yonghong" <yonghong.zhu@intel.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: [Patch] BaseTools: Fix the crash issue when Dynamic structure Pcd use in FDF
Date: Fri, 19 Oct 2018 14:32:12 +0000 [thread overview]
Message-ID: <CB6E33457884FA40993F35157061515CA416C6F7@FMSMSX103.amr.corp.intel.com> (raw)
In-Reply-To: <1539933649-9672-1-git-send-email-yonghong.zhu@intel.com>
Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> -----Original Message-----
> From: edk2-devel [mailto:edk2-devel-bounces@lists.01.org] On Behalf Of
> Yonghong Zhu
> Sent: Friday, October 19, 2018 12:21 AM
> To: edk2-devel@lists.01.org
> Subject: [edk2] [Patch] BaseTools: Fix the crash issue when Dynamic
> structure Pcd use in FDF
>
> The case is use Dynamic structure Pcd in the FDF file.
> Current code already save the Guid, Name and Filed info for those Pcd,
> but it directly use the dict key as [Name, Guid] and cause this crash
> issue.
>
> Fixes: https://bugzilla.tianocore.org/show_bug.cgi?id=1264
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Yonghong Zhu <yonghong.zhu@intel.com>
> ---
> BaseTools/Source/Python/AutoGen/AutoGen.py | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/BaseTools/Source/Python/AutoGen/AutoGen.py
> b/BaseTools/Source/Python/AutoGen/AutoGen.py
> index f2146a7..804f579 100644
> --- a/BaseTools/Source/Python/AutoGen/AutoGen.py
> +++ b/BaseTools/Source/Python/AutoGen/AutoGen.py
> @@ -567,12 +567,12 @@ class WorkspaceAutoGen(AutoGen):
> if (Name, Guid) not in DecPcds:
> EdkLogger.error(
> 'build',
> PARSER_ERROR,
> "PCD (%s.%s) used in FDF is not declared in DEC files." % (Guid,
> Name),
> - File = self.FdfProfile.PcdFileLineDict[Name, Guid][0],
> - Line = self.FdfProfile.PcdFileLineDict[Name, Guid][1]
> + File = self.FdfProfile.PcdFileLineDict[Name, Guid, Fileds][0],
> + Line = self.FdfProfile.PcdFileLineDict[Name, Guid, Fileds][1]
> )
> else:
> # Check whether Dynamic or DynamicEx PCD used in FDF file. If
> used, build break and give a error message.
> if (Name, Guid, TAB_PCDS_FIXED_AT_BUILD) in DecPcdsKey \
> or (Name, Guid, TAB_PCDS_PATCHABLE_IN_MODULE) in
> DecPcdsKey \
> @@ -581,12 +581,12 @@ class WorkspaceAutoGen(AutoGen):
> elif (Name, Guid, TAB_PCDS_DYNAMIC) in DecPcdsKey or (Name,
> Guid, TAB_PCDS_DYNAMIC_EX) in DecPcdsKey:
> EdkLogger.error(
> 'build',
> PARSER_ERROR,
> "Using Dynamic or DynamicEx type of PCD [%s.%s] in FDF file
> is not allowed." % (Guid, Name),
> - File = self.FdfProfile.PcdFileLineDict[Name, Guid][0],
> - Line = self.FdfProfile.PcdFileLineDict[Name, Guid][1]
> + File = self.FdfProfile.PcdFileLineDict[Name, Guid, Fileds][0],
> + Line = self.FdfProfile.PcdFileLineDict[Name, Guid, Fileds][1]
> )
>
> Pa = PlatformAutoGen(self, self.MetaFile, Target, Toolchain, Arch)
> #
> # Explicitly collect platform's dynamic PCDs
> --
> 2.6.1.windows.1
>
> _______________________________________________
> edk2-devel mailing list
> edk2-devel@lists.01.org
> https://lists.01.org/mailman/listinfo/edk2-devel
prev parent reply other threads:[~2018-10-19 14:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-19 7:20 [Patch] BaseTools: Fix the crash issue when Dynamic structure Pcd use in FDF Yonghong Zhu
2018-10-19 14:32 ` Carsey, Jaben [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=CB6E33457884FA40993F35157061515CA416C6F7@FMSMSX103.amr.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