Bug 471340

Summary: callgrind Error: can not open cache simulation output file callgrind.out.pid
Product: [Developer tools] valgrind Reporter: idealeer521
Component: callgrindAssignee: Josef Weidendorfer <josef.weidendorfer>
Status: REPORTED ---    
Severity: crash CC: pjfloyd
Priority: NOR    
Version First Reported In: 3.21.0   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=345414
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description idealeer521 2023-06-22 14:31:05 UTC 
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?
Comment 1 Paul Floyd 2023-06-22 15:26:29 UTC 
Do you have write access where you are running Valgrind?
Comment 2 idealeer521 2023-06-23 02:33:20 UTC 
(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
Comment 3 Paul Floyd 2023-06-23 04:58:16 UTC 
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.
Comment 4 Paul Floyd 2023-06-23 05:01:03 UTC 
See https://bugzilla.mozilla.org/show_bug.cgi?id=1288726 for discussion of seccomp and firefox