added more hooks into dfsan, mostly used for fuzzing with libFuzzer
Diff Detail
Diff Detail
- Build Status
Buildable 9145 Build 9145: arc lint + arc unit
Event Timeline
Comment Actions
my first thought on testing is that I could add a dummy code that
has a strcpy call for example, and define dfsan_weak_hook_strcpy
such that it sets some boolean to true (initially false). And then
assert that the value is changed to true.
But do you think we should have a test for every single hook?
like even the already existing ones (which don't have any tests
as far as I can tell)?
Comment Actions
Yep, something of this kind.
But do you think we should have a test for every single hook?
Yes.
like even the already existing ones (which don't have any tests
as far as I can tell)?
Correct. This is probably my fault. The existing hooks were done as an experiment and later all their uses were removed.