Error getting shm and Segmentation fault

[zhangysh1995]

Program crashes itself (tried with -s):

[zhangys@chcpu12a afl-dyninst]$ ./afl-dyninst -i ../../benchmarks/binary/lavam_binary/base64 -o base64_inst -s 300
Skipping library: libAflDyninst.cpp
Skipping library: libAflDyninst.so
Instrumenting module: base64
Skipping library: ld-linux-x86-64.so.2
Skipping library: libc.so.6
Inserting init callback.
Saving the instrumented binary to base64_inst...
All done! Happy fuzzing!

[zhangys@chcpu12a afl-dyninst]$ ./base64_inst -d ../../lavam/base64/fuzzer_input/rand.b64 
Error getting shm
Segmentation fault

[zhangys@chcpu12a afl-dyninst]$ ./afl-dyninst -i ../../benchmarks/binary/lavam_binary/base64 -o base64_inst -s 500
Skipping library: libAflDyninst.cpp
Skipping library: libAflDyninst.so
Instrumenting module: base64
Skipping library: ld-linux-x86-64.so.2
Skipping library: libc.so.6
Inserting init callback.
Saving the instrumented binary to base64_inst...
All done! Happy fuzzing!

[zhangys@chcpu12a afl-dyninst]$ ./base64_inst -d ../../lavam/base64/fuzzer_input/rand.b64 
Error getting shm
Segmentation fault

It also crashes when using afl-fuzz:

[zhangys@chcpu12a afl]$ ./afl-fuzz -i ../../lavam/base64/fuzzer_input/ -o ../../output/base64_dyn -m none -- ./lavam/base64_inst -d @@
afl-fuzz 2.52b by <[email protected]>
[+] You have 80 CPU cores and 5 runnable tasks (utilization: 6%).
[+] Try parallel jobs - see docs/parallel_fuzzing.txt.
[*] Checking CPU core loadout...
[+] Found a free CPU core, binding to #4.
[*] Checking core_pattern...
[*] Checking CPU scaling governor...
[*] Setting up output directories...
[+] Output directory exists but deemed OK to reuse.
[*] Deleting old session data...
[+] Output dir cleanup successful.
[*] Scanning '../../lavam/base64/fuzzer_input/'...
[+] No auto-generated dictionary tokens to reuse.
[*] Creating hard links for all input files...
[*] Validating target binary...
[*] Attempting dry run with 'id:000000,orig:rand.b64'...
[*] Spinning up the fork server...
[+] All right - fork server is up.

[-] Oops, the program crashed with one of the test cases provided. There are
    several possible explanations:

    - The test case causes known crashes under normal working conditions. If
      so, please remove it. The fuzzer should be seeded with interesting
      inputs - but not ones that cause an outright crash.

    - Least likely, there is a horrible bug in the fuzzer. If other options
      fail, poke <[email protected]> for troubleshooting tips.

[-] PROGRAM ABORT : Test case 'id:000000,orig:rand.b64' results in a crash
         Location : perform_dry_run(), afl-fuzz.c:2852