-
Notifications
You must be signed in to change notification settings - Fork 135
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-slicer hangs somewhere when slicing sqlite-3.38.0 #443
Comments
This commit should fix the problem with unsupported instruction: 9129743, but that is not probably the problem that makes DG hang. As far as I can tell, DG does not hang, the pointer analysis just takes too long. You can try to use |
Thanks a lot! I'll try for this update right away and let you know the result. |
Hi, I've tried the branch
When running in debug mode of dg, the output is:
The above tests were run in the environment where sqlite3 is compiled without any compile options. However, when I compiled sqlite3 with the command:
Besides, when I set Could you please tell me how to solve it? |
How long does it take before the crash? I cannot reproduce that.
I optimized that part a bit.
The PTA analysis seems to be too inefficient to analyse this piece of code. |
dg crashes as soon as it starts running and the crashed bitcode file is attached below. |
You can try the commit above that should fix the crash. The runtime will, however, not change... |
Hi, llvm-slicer hung when I tried to do backward slice on sqlite-3.38.0 with following command:
The output of llvm-slicer is :
After printing the message above, llvm-slicer hung and didn't print any message anymore.
I also tried to compile dg with debug flag and sanitizer command
DCMAKE_BUILD_TYPE=Debug -DUSE_SANITIZERS=ON
, and then I got assertion failure:I use gllvm to produce the bitcode file of sqlite3, and the running environment is as follows:
Could you please tell me how to solve it? The bitcode file is attached below.
sqlite3_bitcode.zip
The text was updated successfully, but these errors were encountered: