issue1941 - fuzz sock_addr/ops/xdp

[vpidatala94]

Description

With this pull-request we are providing an extra argument to core helper fuzz tests "-helper" that helps fuzz test helper functions specific helper functions.

In LLVM initialize, after processing our custom arg we are working towards remove it before the libfuzzer can process it.

Testing

fuzz testing.

Documentation

Reference --
https://llvm.org/docs/LibFuzzer.html
https://github.com/google/fuzzing/blob/master/tutorial/libFuzzerTutorial.md

[vpidatala94]

UNIT test output :
PS C:\Users\vpidatala\Code\ebpf-Windows\ebpf-for-windows\x64\Release> .\core_helper_fuzzer.exe core_helper_corpus -max_len=139 -runs=1000 -use_value_profile=1 -artifact_prefix=Artifacts\ -helper sockaddr
WARNING: Failed to find function "__sanitizer_acquire_crash_state".
WARNING: Failed to find function "__sanitizer_print_stack_trace".
WARNING: Failed to find function "__sanitizer_set_death_callback".
INFO: Running with entropic power schedule (0xFF, 100).
INFO: Seed: 3385511717
INFO: 20 files found in core_helper_corpus
INFO: seed corpus: files: 20 min: 1b max: 37b total: 189b rss: 29Mb
#21 INITED exec/s: 0 rss: 29Mb
WARNING: no interesting inputs were found so far. Is the code instrumented for coverage?
This may also happen if the target rejected all inputs we tried so far
#1000 DONE corp: 1/1b lim: 11 exec/s: 0 rss: 29Mb
Done 1000 runs in 0 second(s)
PS C:\Users\vpidatala\Code\ebpf-Windows\ebpf-for-windows\x64\Release> cd .\Artifacts
PS C:\Users\vpidatala\Code\ebpf-Windows\ebpf-for-windows\x64\Release\Artifacts> ls

---

nothing generated in artifacts is OK, as they are no expected crashes

[saxena-anurag]

@vpidatala94 there are some open comments in this PR. Can you have a look.