Fuzz test mode requirements?

[dwi...@protonmail.com]

Hi,

Are there any special requirements for running the fuzz test mode? I have followed the example at http://drmemory.org/docs/page_fuzzer.html, but when running e.g.

./DrMemory-Linux-2.0.1-2/bin/drmemory -fuzz -fuzz_module a.out -fuzz_function DrMemFuzzFunc -fuzz_num_args 2 -fuzz_data_idx 0 -fuzz_size_idx 1 -fuzz_num_iters 100

(or just running with -fuzz) no fuzzing is done. It just looks like it runs the program (call main) once in the same way as without any -fuzz* arguments.

dwight@l:~/Development/test/drmemory$ ./DrMemory-Linux-2.0.1-2/bin/drmemory -v -fuzz -fuzz_module a.out -fuzz_function DrMemFuzzFunc -fuzz_num_args 2 -fuzz_data_idx 0 -fuzz_size_idx 1 -fuzz_num_iters 100 -- a.out
INFO: targeting application: "/home/dwight/Development/test/drmemory/a.out"
INFO: app cmdline: "a.out" 
INFO: logdir is "/home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/drmemory/logs"
INFO: symcache_dir is "/home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/drmemory/logs/symcache"
INFO: DynamoRIO configuration directory is /home/dwight/.dynamorio
INFO: configuring a.out pid=22434 dr_ops="-disable_traces -bb_single_restore_prefix -max_bb_instrs 256 -vm_size 256M -no_enable_reset -no_vm_base_near_app -logdir `/home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/drmemory/logs/dynamorio` "
INFO: configuring client "/home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/bin/release/libdrmemorylib.so" ops="`-fuzz` `-fuzz_module` `a.out` `-fuzz_function` `DrMemFuzzFunc` `-fuzz_num_args` `2` `-fuzz_data_idx` `0` `-fuzz_size_idx` `1` `-fuzz_num_iters` `100` -logdir `/home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/drmemory/logs` -symcache_dir `/home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/drmemory/logs/symcache` -resfile 22434 "
~~Dr.M~~ Dr. Memory version 2.0.1
~~Dr.M~~ WARNING: application is missing line number information.
~~Dr.M~~ 
~~Dr.M~~ NO ERRORS FOUND:
~~Dr.M~~ 0 unique, 0 total unaddressable access(es)
~~Dr.M~~ 0 unique, 0 total uninitialized access(es)
~~Dr.M~~ 0 unique, 0 total invalid heap argument(s)
~~Dr.M~~ 0 unique, 0 total warning(s)
~~Dr.M~~ 0 unique, 0 total, 0 byte(s) of leak(s)
~~Dr.M~~ 0 unique, 0 total, 0 byte(s) of possible leak(s)
~~Dr.M~~ ERRORS IGNORED:
~~Dr.M~~ 14 unique, 17 total, 4943 byte(s) of still-reachable allocation(s)
~~Dr.M~~ (re-run with "-show_reachable" for details)
~~Dr.M~~ Details: /home/dwight/Development/test/drmemory/DrMemory-Linux-2.0.1-2/drmemory/logs/DrMemory-a.out.22434.000/results.txt

I must have misunderstood something... Any ideas?

Running on Linux (Ubuntu 18.04, tested both 32 and 64 bit binaries), fuzz target is a C function. Same problem with -light, nothing reported when using -debug -dr_debug -pause_at_assert.

// Dwight

[Juaneme]

Hi,

I have the same issue

Still have the problem ?