booFuzz vs libFuzzer confusion

[avgNobody]

Hi,
So I'm a bit confused. If this is using the libfuzzer engine, why do you have it using booFuzz? Why is that being linked in the make file?

[ant4g0nist]

hey. Sorry for the confusion. booFuzz has nothing to do with the booFuzz you are seeing in Sloth. it's just a random name I used for the compiled example library!

[avgNobody]

Thanks! Also, I was looking around to see why you included libhwui.so I guess it was aa Skia library? I don't see it being used anywhere. :)

[avgNobody]

Android seems to have moved around this library and a few of the graphics dependencies in the later versions.

[ant4g0nist]

When I was building, the example project depended on the Android version. That's why the libhwui :)

[avgNobody]

I managed to get it all building, but when running the command:
SLOTH_TARGET_LIBRARY=/rootfs/system/lib64/libBooFuzz.so ./sloth /rootfs/boofuzz test/
I seem to be getting a segfault. Have you run into that or helped anyone that ran into this issue?
My backtrace seems to be
#0 __memset_avx2_unaligned_erms () at ../sysdeps/x86_64/multiarch/memset-vec-unaligned-erms.S:200
#1 0x00007f6c29c54779 in zero_bss (elf_bss=365072230992, last_bss=, prot=) at /sloth/src/qemu/linux-user/elfload.c:1817
#2 load_elf_image (image_name=, image_fd=, info=, pinterp_name=0x7ffd43389d88, bprm_buf=) at /sloth/src/qemu/linux-user/elfload.c:2550
#3 0x00007f6c29c52dd5 in load_elf_binary (bprm=0x7ffd4338a0e0, info=0x7ffd43389fe0) at /sloth/src/qemu/linux-user/elfload.c:2877
#4 0x00007f6c29c56531 in loader_exec (fdexec=, filename=, argv=, envp=, regs=0x7ffd4338a520, infop=0x7ffd43389fe0, bprm=0x7ffd4338a0e0)
at /sloth/src/qemu/linux-user/linuxload.c:147
#5 0x00007f6c29c330e6 in libQemuInit (argc=2, argv=, envp=) at /sloth/src/qemu/linux-user/main.c:849
#6 0x0000000000404a37 in main ()

[avgNobody]

Oh sorry. I forgot I had an open question. I figured it out, so I'm good now. Thanks! And great stuff on Sloth man. I appreciate the work you put into it.