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
Hi! I got the following error
Running phase: Initialization ( 0.00s )
Running phase: LLVM ( 0.03s )
Running phase: Providers initialization ( 0.03s )
Running phase: Input binary to LLVM IR decoding ( 1.31s )
LLVM ERROR: Could not acquire a cryptographic context: Unknown error (0x7F)
Error: Decompilation to LLVM IR failed
Windows 7, 64b version of decompiler. What could be the problem?
The text was updated successfully, but these errors were encountered:
Hi. I believe this is caused by insufficient memory in the system when decompiling larger files (see also #73 and #47). Questions:
Could you attach the input binary file that you are trying to decompile?
How much RAM do you have?
Does this happen when decompiling all files, or just with some of them?
You can try decompiling the file as follows, which will disable the default memory limit (half of system RAM). However, beware that the decompilation may eat all your memory:
@asimaranov Does the issue persist or were you able to resolve it? If the issue persists, please provide answers to the four questions above. If you were able to resolve it, please tell us what you have done. This may be handy for other users who stumble upon the same error in the future.
Yes, adding the '--no-memory-limit' parameter solves the thrown exception. Finally, bin2llvmir uses nearly 3G of memory, my computer's memory is 32G. (google translation)
Hi! I got the following error
Running phase: Initialization ( 0.00s )
Running phase: LLVM ( 0.03s )
Running phase: Providers initialization ( 0.03s )
Running phase: Input binary to LLVM IR decoding ( 1.31s )
LLVM ERROR: Could not acquire a cryptographic context: Unknown error (0x7F)
Error: Decompilation to LLVM IR failed
Windows 7, 64b version of decompiler. What could be the problem?
The text was updated successfully, but these errors were encountered: