-
Notifications
You must be signed in to change notification settings - Fork 436
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 when using SVF on Ceph #1392
Comments
@jumormt could you take a look at this issue? |
@Louise4one would you upload the bc file and also give the debug trace of your stack? |
@Louise4one could you upload your bc or provide a link where we could download or compile? |
GitHub doesn't support bitcode file type, I put it in the zip file. But the file size is still over the limit of GitHub. I found your unsw e-mail on the internet. I deliver the bitcode file via e-mail, named with GitHub SVF issues #1392. |
I have pulled the latest version of SVF and ran wpa on the same radosgw.bc again. However it ends up in another assertion:
|
@bjjwwang could you fix this? It is caused by recent floating point handling in AE |
Should have just been fixed. |
I tried to use SVF on Ceph (version 18.2.1). First I used WLLVM (LLVM version 16.0.0, Clang version 10.0.0) to generate Ceph bitcode, then I wanted to run wpa on Ceph RGW. But I countered with assertion below:
I think it might be an unavoidable warning if SVF is used on such complex project, so I just ignored it. Then another assertion came out:
What leads to this assertion? Should I ignored this one again? If not, how can I solve this problem?
By the way, I tried to turn off all assertions in SVF and ran Ceph RGW again. However, segmentation fault happened this time, and the gdb information was:
How can I solve the problem?
The text was updated successfully, but these errors were encountered: