[Heaptrack] [Bug 394557] New: CMake error when boost filesystem is missing

[Thomas McGuire]

https://bugs.kde.org/show_bug.cgi?id=394557

Bug ID: 394557
   Summary: CMake error when boost filesystem is missing
   Product: Heaptrack
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: normal
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: mcgu...@kde.org
  Target Milestone: ---

When boost-filesystem is not installed, I get the following CMake error when
trying to build heaptrack:

CMake Error at tests/auto/CMakeLists.txt:20 (if):
  if given arguments:

"AND" "ON"

  Unknown arguments specified

The error disappears when installing boost-filesystem.
I expect that a missing boost-filesystem dependency is listed as a failed
dependency in a more user-friendly way.

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 380985] Incorrect library used when app relies on rpath

[Thomas McGuire]

https://bugs.kde.org/show_bug.cgi?id=380985

Thomas McGuire <mcgu...@kde.org> changed:

   What|Removed |Added

 Resolution|--- |INVALID
 Status|UNCONFIRMED |RESOLVED

--- Comment #2 from Thomas McGuire <mcgu...@kde.org> ---
Upps, this was a user problem, the executable accidentally loaded the wrong
Qt...

-- 
You are receiving this mail because:
You are watching all bug changes.

[Heaptrack] [Bug 380985] New: Incorrect library used when app relies on rpath

[Thomas McGuire]

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.

[Heaptrack] [Bug 379660] New: Collapse template arguments in flamegraph

[Thomas McGuire]

https://bugs.kde.org/show_bug.cgi?id=379660

Bug ID: 379660
   Summary: Collapse template arguments in flamegraph
   Product: Heaptrack
   Version: unspecified
  Platform: Compiled Sources
OS: Linux
Status: UNCONFIRMED
  Severity: wishlist
  Priority: NOR
 Component: general
  Assignee: m...@milianw.de
  Reporter: mcgu...@kde.org
  Target Milestone: ---

When running heaptrack on something that uses a lot of templates, like
std::string, the flamegraph becomes unreadable because all the template
arguments are obscuring the function name. Some suggestions:

- Elide the function name in the middle instead of cutting it off a the end
- Collapse long tempate arguments: Instead of "std::map::operator[](std::string )", say just
"std::map<...>::operator[](std::string )"

-- 
You are receiving this mail because:
You are watching all bug changes.