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

Assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed #1623

Open
Rexxar-Jack-Remar opened this issue Jan 8, 2025 · 4 comments

Comments

@Rexxar-Jack-Remar
Copy link
Contributor

Rexxar-Jack-Remar commented Jan 8, 2025

After updating SVF to the newest version 32c2a51, I encountered a problem.

(py38) root@45cb62a8ed4a:~/exp/nginx-1.27.3-16 # wpa -ander nginx-1.27.3-16.bc 
vcall gep idx not constantint
vcall gep idx not constantint
vcall gep idx not constantint
vcall gep idx not constantint
vcall gep idx not constantint
vcall gep idx not constantint
vcall gep idx not constantint
vcall gep idx not constantint
wpa: /opt/llvm-16.0.4.obj/include/llvm/ADT/APInt.h:1497: uint64_t llvm::APInt::getZExtValue() const: Assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed.

The bitcode file is attached. Could you give me a hand?

bc.zip

@Rexxar-Jack-Remar Rexxar-Jack-Remar changed the title Two problems: assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed & wpa could not end assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed Jan 8, 2025
@Rexxar-Jack-Remar Rexxar-Jack-Remar changed the title assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed Assertion `getActiveBits() <= 64 && "Too many bits for uint64_t"' failed Jan 8, 2025
@jumormt
Copy link
Contributor

jumormt commented Jan 8, 2025

It is like an internal crash in LLVM when calling intValue->getSExtValue(), where intValue is llvm::ConstantInt

@Rexxar-Jack-Remar
Copy link
Contributor Author

It is like an internal crash in LLVM when calling intValue->getSExtValue(), where intValue is llvm::ConstantInt

I tried the former version of SVF, and this error didn't occur. I guess there is something wrong with transformation from LLVM IR to SVF IR.

@yuleisui
Copy link
Collaborator

yuleisui commented Jan 8, 2025

Should be fixed via #1624. Pls try and let us know.

@Rexxar-Jack-Remar
Copy link
Contributor Author

Should be fixed via #1624. Pls try and let us know.

That really works. Thank you for your help!

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

3 participants