https://bugs.kde.org/show_bug.cgi?id=380985
Bug ID: 380985
Summary: Incorrect library used when app relies on rpath
Product: Heaptrack
Version: unspecified
Platform: Other
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: m...@milianw.de
Reporter: mcgu...@kde.org
Target Milestone: ---
I was using heaptrack on an app that uses a Qt4 installed in
/home/thomas/install/opt/qt-4-desktop. That application uses rpath to find the
Qt4 libraries without the need to set LD_LIBRARY_PATH. My LD_LIBRARY_PATH
actually had the Qt libraries from /usr/lib64 in them.
heaptrack used the incorrect Qt from /usr/lib64, resulting in backtraces with
lots of unresolved symbols. I spotted that the wrong library was used in the
tooltip of the flame graph, which shows the library of an entry,
As a workaround, I changed my LD_LIBRARY_PATH. However I think heaptrack should
do the correct thing and follow the rpath, as otherwise the behaviour can be
highly confusing if one doesn't spot the incorrect library by chance.
--
You are receiving this mail because:
You are watching all bug changes.
