[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

@travis-downs this issue was fixed and is no longer monitored, if you have a new bug report against perf, can you please open a new issue? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.laun

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

> we can't think of anything besides gdb, valgrind, and libunwind that uses /usr/lib/debug That seems like quite an incredible statement! I can imagine that many debugging and profiling tools will want symbols. For example, this change is breaking perf right now, as it looks for say libc symbols

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

This bug was fixed in the package valgrind - 1:3.14.0-2ubuntu4 --- valgrind (1:3.14.0-2ubuntu4) disco; urgency=medium * s390x Fix vector facility bit. valgrind (1:3.14.0-2ubuntu3) disco; urgency=medium * Cherrypick s390x/z13 fixes from valgrind master (3.15) LP: #1799696 valgri

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

A fix for this bug was uploaded on the 10th but didn't seem to migrate out of -proposed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

** Tags added: id-5c3776fa4cafca4421242879 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn't work in disco [Fatal error at startup: a funct

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

from IRC discussion, we know that gdb is not affected provided that packages provide .build-id (which glibc does) and we can't think of anything besides gdb, valgrind, and libunwind that uses /usr/lib/debug; so it looks like we should just extend valgrind's lookup path. ** Changed in: valgrind (Ub

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

dh_strip in debhelper v9 mode doesn't use the filename anymore, so gdb should not affected. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to base-files in Ubuntu. https://bugs.launchpad.net/bugs/1808508 Title: Valgrind doesn

[Touch-packages] [Bug 1808508] Re: Valgrind doesn't work in disco [Fatal error at startup: a function redirection which is mandatory for this platform-tool combination cannot be set up.]

This is related to the usrmerge transition. On a freshly debootstrapped disco environment, /lib is a symlink to /usr/lib, which means the canonical path for the debug symbols as looked for by valgrind is /usr/lib/debug/usr/lib/x86_64-linux-gnu/ld-2.28.so which does not exist; only /usr/lib/debug/l