-
Notifications
You must be signed in to change notification settings - Fork 14
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
fix: prevent ub, always havoc after malloc #114
Conversation
priyasiddharth
commented
Nov 4, 2021
- Document differences between seahorn, fuzz, klee and smack -- in some cases, malloc fails, in others it does not
- Rename malloc to malloc_havoc to clarify what is expected to happen
LGTM |
FUZZ got failing. @danblitzhou is that necessary to enable fuzzing test under Seahorn CI?
|
this seems like a mistake, we have a separate fuzzing dockerfile; will turn this off in a PR |
Codecov Report
@@ Coverage Diff @@
## master #114 +/- ##
==========================================
+ Coverage 93.74% 95.12% +1.37%
==========================================
Files 159 159
Lines 4907 4919 +12
==========================================
+ Hits 4600 4679 +79
+ Misses 307 240 -67
Continue to review full report at Codecov.
|
g_fuzz_data_iterator += sizeof(bool); | ||
|
||
return res; | ||
return (tmp > 0); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we assuming fuzz always returns a true value after invoking nd_bool
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, we get the next sizeof(bool)
data. If it is zero then we return false
.
1. Document differences between seahorn, fuzz, klee and smack -- in some cases, malloc fails, in others it does not 2. Rename malloc to malloc_havoc to clarify what is expected to happen
2721bbb
to
4e28073
Compare
|