SUMMARY When I use this cmd: `valgrind --tool=callgrind --trace-children=yes unbound -d -c /etc/unbound/unbound.conf` to debug unbound, it shows: ==19295== Error: can not open cache simulation output file `callgrind.out.19295' ==19295== could not unlink /tmp/vgdb-pipe-from-vgdb-to-19295-by-unbound-on-??? ==19295== could not unlink /tmp/vgdb-pipe-to-vgdb-from-19295-by-unbound-on-??? ==19295== could not unlink /tmp/vgdb-pipe-shared-mem-vgdb-19295-by-unbound-on-??? Do you have similar issues?
Do you have write access where you are running Valgrind?
(In reply to Paul Floyd from comment #1) > Do you have write access where you are running Valgrind? Yes. I tested three software. The former two are good, but for unbound, Valgrind just made the error above. drwxr-xr-x 10 root root 12288 Jun 22 14:00 bind-9.18.12 drwxr-xr-x 18 root root 4096 Jun 22 11:47 knot-resolver-5.6.0 drwxrwxr-x 27 root root 12288 Jun 23 02:30 unbound-1.17.1
In that case I guess that unbound is using capabilities. If so there's not much that can be done unless you can build a version that does not use capabilities.
See https://bugzilla.mozilla.org/show_bug.cgi?id=1288726 for discussion of seccomp and firefox