You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parser does not take into account the case where we have File -> GUID Defined Section -> PE32 image/UI.
The screenshot below shows an example of valid parsing by UEFITool:
If we run uefi-firmware-parser on the test file in verbose mode (uefi-firmware-parser -b --verbose Volume_FFSv2_5C60F367-A505-419A-859E-2A4FF6CA6FE5.vol), we get the following result: log.txt.
As far as I can see, it successfully performs the decompression, but it does not process the data with respect to parent file.
The parser does not take into account the case where we have
File -> GUID Defined Section -> PE32 image/UI
.The screenshot below shows an example of valid parsing by UEFITool:
If we run
uefi-firmware-parser
on the test file in verbose mode (uefi-firmware-parser -b --verbose Volume_FFSv2_5C60F367-A505-419A-859E-2A4FF6CA6FE5.vol
), we get the following result: log.txt.As far as I can see, it successfully performs the decompression, but it does not process the data with respect to parent file.
The test volume is attached:
Volume_FFSv2_5C60F367-A505-419A-859E-2A4FF6CA6FE5.vol.zip
The text was updated successfully, but these errors were encountered: