You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, I never fuzzed on Android - the Android port is work of other people (both inside and inside my company) and I have little knowledge on how it works (should work).
You said that you get warnings about detect_odr_violation if you add . Is this the only problem? Because if so, you can simply remove it from sanitizers.c
First of all, I never fuzzed on Android - the Android port is work of other people (both inside and inside my company) and I have little knowledge on how it works (should work).
You said that you get warnings about detect_odr_violation if you add . Is this the only problem? Because if so, you can simply remove it from sanitizers.c
Thanks for your reply, fix detect_odr_violation is easy. But I still cannot get any coverage info :(
Is there any doc about building harness on Android?
First of all, I never fuzzed on Android - the Android port is work of other people (both inside and inside my company) and I have little knowledge on how it works (should work).
You said that you get warnings about detect_odr_violation if you add . Is this the only problem? Because if so, you can simply remove it from sanitizers.c
Thanks for your reply, fix detect_odr_violation is easy. But I still cannot get any coverage info :( Is there any doc about building harness on Android?
I got same situation as #342
I try to add
-fsanitize-coverage=trace-pc-guard,trace-cmp,trace-div,indirect-calls
, but I got many warnings:I checked google's doc :
in
Application.mk
:For each module in your
Android.mk
:so I modified my demo as follow:
After
ndk-build
, I test it on my pixel2 :It seems ASAN works fine.
But when I try to fuzzing
fuzz_test
with honggfuzz, I find I cannot get any coverage infomation :What I did wrong? Could you suggest something, please?
The text was updated successfully, but these errors were encountered: