[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid

2023-11-14 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=471340 Mark Wielaard changed: What|Removed |Added See Also||https://bugs.kde.org/show_b

[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid

2023-06-22 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=471340 --- Comment #4 from Paul Floyd --- See https://bugzilla.mozilla.org/show_bug.cgi?id=1288726 for discussion of seccomp and firefox -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid

2023-06-22 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=471340 --- Comment #3 from Paul Floyd --- 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. -- You are receiving this mail because: You are

[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid

2023-06-22 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=471340 --- Comment #2 from idealeer...@gmail.com --- (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

[valgrind] [Bug 471340] callgrind Error: can not open cache simulation output file callgrind.out.pid

2023-06-22 Thread Paul Floyd
https://bugs.kde.org/show_bug.cgi?id=471340 Paul Floyd changed: What|Removed |Added CC||pjfl...@wanadoo.fr --- Comment #1 from Paul Floyd