https://bugs.kde.org/show_bug.cgi?id=435732
Paul Floyd changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #10 from Paul Floyd ---
I do see a difference because of debuginfo, and pushed a second change for
that. If the nightlies are clean I'll close this (and 403802)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #9 from Paul Floyd ---
In the nightly tests I see that this is failing for several platforms still
(s390x Fedora 34, amd64 Fedora 34 to 36).
It could be that the difference is down to whether debuginfo is
installed/available for libstfc++.
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #8 from Paul Floyd ---
I made the suppression even broader. It's gone from failing to passing for me
on Fedora 34 / GCC 11.2.1
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #7 from Paul Floyd ---
I think that an even broader suppression for the stdio buffer should be OK, as
follows
diff --git a/memcheck/tests/libstdc++.supp b/memcheck/tests/libstdc++.supp
index 520e6613a..3cd2e628d 100644
---
https://bugs.kde.org/show_bug.cgi?id=435732
Sam James changed:
What|Removed |Added
CC||s...@gentoo.org
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #6 from Paul Floyd ---
We should be looking at leak_cpp_interior.stderr.diff-64bit rather than
leak_cpp_interior.stderr.diff (same for 403802)
With g++ 9.2 on RHEL 7 I get a similar failure, but without the still reachable
that I get with
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #5 from Paul Floyd ---
The doesn't reproduce with g++11 (FreeBSD Ports Collection) 11.2.0
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=435732
Mark Wielaard changed:
What|Removed |Added
See Also||https://bugs.kde.org/show_b
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #3 from Paul Floyd ---
I can reproduce this problem with a much older g++, 5.3.0.
Running the testcase in place gives the following information
==13544== 72,704 bytes in 1 blocks are still reachable in loss record 10 of 10
==13544==at
https://bugs.kde.org/show_bug.cgi?id=435732
--- Comment #2 from Paul Floyd ---
Hmm. The stuff that I wrote for C++11 was mostly right, but it is wrong for
C++03 and earlier.
libstdc++ prior to C++11 jus has a pointer in std::string. This points to
memory containing the layout
https://bugs.kde.org/show_bug.cgi?id=435732
Paul Floyd changed:
What|Removed |Added
CC||pjfl...@wanadoo.fr
--- Comment #1 from Paul Floyd
12 matches
Mail list logo
