https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #6 from Matt Whitlock ---
(In reply to Milian Wolff from comment #5)
> can you please try the latest master and see if you are still seeing this
> breakage?
Yes, that fixed it. I no longer get nonsense traces in Heaptrack, and I
actually ma
https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #5 from Milian Wolff ---
Hey Matt,
can you please try the latest master and see if you are still seeing this
breakage?
Quite frankly, I'm super stumped by this breakage as I mentioned in the commit
message for the workaround I implemented
https://bugs.kde.org/show_bug.cgi?id=439897
Milian Wolff changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/sdk/
|
https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #3 from Milian Wolff ---
I think I now found a case where I get bogus backtraces too. I'll investigate
and see if there's a way to fix this within heaptrack's libbacktrace
thanks
--
You are receiving this mail because:
You are watching al
https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #2 from Matt Whitlock ---
(In reply to Milian Wolff from comment #1)
> Since you are using gentoo: Are the debug symbols you are using for
> plasmashell and qt and so forth matching the build that you profiled?
Yes. The debug symbols get in
https://bugs.kde.org/show_bug.cgi?id=439897
--- Comment #1 from Milian Wolff ---
Hey there, thanks for your report.
Since you are using gentoo: Are the debug symbols you are using for plasmashell
and qt and so forth matching the build that you profiled?
Is this easily reproducible for me someho
