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

llvm:symbol-entry errors on llvm 11.0 with x86-64 binaries compiled on windows #1553

Open
matt-j-griffin opened this issue Sep 28, 2022 · 1 comment

Comments

@matt-j-griffin
Copy link
Contributor

matt-j-griffin commented Sep 28, 2022

Attempting to disassemble a windows binary produces the following error:

Failed to build the project: attribute "llvm:symbol-entry" didn't provide a
value for the field "value"

I have previously been using the command bap ./binary.dll -dbir --optimization-level=3 with success in prior versions of bap, though now when I roll back to 2.2.0, 2.3.0 and 2.4.0 I get the same error. This error also occurs with bap specification and bap objdump. I assume this has something to do with the version of LLVM but I am not sure how to change this in BAP?

For reference this is the output of file binary.dll

binary.dll: PE32+ executable (DLL) (GUI) x86-64, for MS Windows

The binary can be disassembled with --loader=raw successfully, but this loses the exported dll symbols.

Invoking bap --llvm-version returns 11.0.1.

@matt-j-griffin
Copy link
Contributor Author

matt-j-griffin commented Sep 28, 2022

This does not occur when I use the docker image so it is probably an issue with my system, I was using debian wsl2. The version of llvm in the container is 9.0.

@matt-j-griffin matt-j-griffin changed the title llvm:symbol-entry errors with x86-64 binaries compiled on windows llvm:symbol-entry errors on llvm 11.0 with x86-64 binaries compiled on windows Oct 5, 2022
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

No branches or pull requests

1 participant