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

use -mllvm -bcf param , there is no response #121

Open
phiall opened this issue May 16, 2018 · 3 comments
Open

use -mllvm -bcf param , there is no response #121

phiall opened this issue May 16, 2018 · 3 comments

Comments

@phiall
Copy link

phiall commented May 16, 2018

When I use o-llvm compiler where -mllvm -bcf -mllvm -bcf_loop=1 -mllvm -bcf_prob=20 param, there is no response, even one day.
Similarly, I hava integrated with XCode 9.2, but there are exceptions when build.
The Exceptions:

  1. parser at end of file
  2. Per-module optimization passes
  3. Running pass 'CallGraph Pass Manager' on module '/Users/i-mac/Files/lhp/wzqqp_ios/frameworks/runtime-src/Classes/LuaAssert/AESEncrypt.cpp'.
  4. Running pass 'Bit-Tracking Dead Code Elimination' on function '@_ZNSt3__120__throw_length_errorEPKc'
    clang-4.0: error: unable to execute command: Segmentation fault: 11
    clang-4.0: error: clang frontend command failed due to signal (use -v to see invocation)
    Obfuscator-LLVM clang version 4.0.1 (based on Obfuscator-LLVM 4.0.1)
    Target: arm-apple-darwin16.7.0
    Thread model: posix
    InstalledDir: /Users/i-mac/Files/lhp/obfuscator/build/bin
    clang-4.0: note: diagnostic msg: PLEASE submit a bug report to http://o-llvm.org and include the crash backtrace, preprocessed source, and associated run script.
    clang-4.0: note: diagnostic msg:

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:
Preprocessed source(s) and associated run script(s) are located at:
clang-4.0: note: diagnostic msg: /var/folders/cs/lthfm4pn66xcqck3pd73vw940000gn/T/AESEncrypt-a20999.cpp
clang-4.0: note: diagnostic msg: /var/folders/cs/lthfm4pn66xcqck3pd73vw940000gn/T/AESEncrypt-a20999.sh
clang-4.0: note: diagnostic msg: Crash backtrace is located in
clang-4.0: note: diagnostic msg: /Users/i-mac/Library/Logs/DiagnosticReports/clang-4.0__.crash
clang-4.0: note: diagnostic msg: (choose the .crash file that corresponds to your crash)
clang-4.0: note: diagnostic msg:


Command /Users/i-mac/Files/lhp/obfuscator/build/bin/clang failed with exit code 254

@phiall
Copy link
Author

phiall commented May 16, 2018

Is there any way to fix it ?

@MrManiak
Copy link

You have to use the patch in the pull requests.

@xabiugarte
Copy link

For completeness, it seems the patch is this one: #76

At least, it worked for me.

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