[Kernel-packages] [Bug 1875274] Re: usrmerge breaks perf symbol lookup

2020-07-17 Thread Paolo Pisati
Already fixed upstream, and awaiting in the stable branch linux-5.4.y: 807cc607f129 perf symbols: Fix debuginfo search for Ubuntu -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875274

[Kernel-packages] [Bug 1875274] Re: usrmerge breaks perf symbol lookup

2020-07-16 Thread Paolo Pisati
Hi Travis, do you have an easy reproducer for this? I'm not familiar with perf, so a step to step guide would help me a lot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title:

[Kernel-packages] [Bug 1875274] Re: usrmerge breaks perf symbol lookup

2020-07-05 Thread Travis Downs
This is still broken in 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875274 Title: usrmerge breaks perf symbol lookup Status in linux package in Ubuntu: Confirmed Bug

[Kernel-packages] [Bug 1875274] Re: usrmerge breaks perf symbol lookup

2020-04-27 Thread Travis Downs
apport information ** Tags added: apport-collected eoan ** Description changed: In 19.10, perf cannot find the symbols for libc even after installing libc-dbg. The symbols for libc are in: /usr/lib/debug/lib/x86_64-linux-gnu/ but libc is in: /usr/lib/x86_64-linux-gnu/

[Kernel-packages] [Bug 1875274] Re: usrmerge breaks perf symbol lookup

2020-04-26 Thread Travis Downs
This is the same issue as: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1808508 ... where the fix was to manually path the Valgrind debug info lookup path, but this doesn't seem feasible for every application that might care about symbols. Better to put the symbols in the right place