Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PDB found, but could not be loaded (E_PDB_MAX) #353

Closed
DefaultRyan opened this issue Mar 12, 2021 · 4 comments · Fixed by #399
Closed

PDB found, but could not be loaded (E_PDB_MAX) #353

DefaultRyan opened this issue Mar 12, 2021 · 4 comments · Fixed by #399

Comments

@DefaultRyan
Copy link
Member

I've got my sym path and cache set, and when I enable pdb tracing, it appears that the pdb is found, but I'm getting E_PDB_MAX errors, and there is no documentation on what this error means, or how to fix it.

I get output that looks like this:

Microsoft.UI.Xaml.Controls.dll : error ERR997.ExceptionLoadingPdb : BA2002 : 'Microsoft.UI.Xaml.Controls.dll' was not evaluated for check 'DoNotIncorporateVulnerableDependencies' because its PDB could not be loaded (E_PDB_MAX).
Microsoft.UI.Xaml.Controls.dll : warning TRC001.PdbLoad : BA2002 : Could not locate the PDB for 'Microsoft.UI.Xaml.Controls.dll'. Probing details:
  Examined PDB path: 'C:\a\1\s\BuildOutput\obj\arm64fre\controls\dev\dll\Microsoft.UI.Xaml.Controls.pdb'. HResult: E_PDB_NOT_FOUND.
  Examined PDB path: 'd:\dbg\sym\Microsoft.UI.Xaml.Controls.pdb\D370C85C6E864E32A9AEE2A6DE425F2A1\Microsoft.UI.Xaml.Controls.pdb'. HResult: S_OK.

The traces indicate that the PDB was found in the cache path, and I see a PDB file there. So, what's the deal with E_PDB_MAX?

@eddynaka
Copy link
Contributor

eddynaka commented Jun 1, 2021

Hi @DefaultRyan , sorry for the delay.
Looking at the dll/pdb again, it looks like the pdb is stripped and with that, binskim can not do the analysis.

@CurtHagenlocher
Copy link

I believe in previous versions of BinSkim, this returned an easier-to-understand error "(Pdb is stripped of cv (CodeView) info)".

@eddynaka eddynaka linked a pull request Jul 15, 2021 that will close this issue
@eddynaka
Copy link
Contributor

Hi @CurtHagenlocher , with the PR marked above we fixed this issue.
soon we will release a new version.

@eddynaka
Copy link
Contributor

Hi @DefaultRyan, with the PR marked above we fixed this issue.
soon we will release a new version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants