[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

2016-03-03 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #11 from Ivo Raisr --- Yes, it can be done with just one FREERES_DONE hook. But it means we need to pass argument(s) to it (which __freeres functions to call) and this will involve some extra code for all supported architectures. See invoker

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-03-02 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #9 from Ivo Raisr --- Steven, would you be able to prepare a patch for Linux using similar technique? I cannot currently devote to developing it for a while. Beware that Linux has ppoll and pselect6 syscalls. And pselect6 encodes the last ar

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-03-02 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Attachment #97632|0 |1 is obsolete||

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-03-01 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #7 from Ivo Raisr --- The attached patch has two problems: - it modifies a client memory which may be read-only (see for example bugs for modifying env) - it modifies a client memory and does not restore the changes after syscall -- You ar

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-03-01 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 --- Comment #6 from Ivo Raisr --- Steven, thank you for the test case provided and a suggested fix. Indeed, simple things are very often also effective. I will prepare patch for Linux as well and have that reviewed. -- You are receiving this mail beca

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-03-01 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Attachment #97584|0 |1 is obsolete||

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-03-01 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Status|UNCONFIRMED |C

[valgrind] [Bug 359871] Incorrect mask handling in ppoll

2016-02-29 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359871 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #2 from Ivo Raisr ---

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-25 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #9 from Ivo Raisr --- Regression testing on Linux and Solaris went fine. Together with patch for https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69945 we see now: ==1862== HEAP SUMMARY: ==1862== in use at exit: 0 bytes in 0 blocks ==1862==

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-25 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #8 from Ivo Raisr --- Created attachment 97556 --> https://bugs.kde.org/attachment.cgi?id=97556&action=edit patch for Linux and Solaris calling __gnu_cxx::__freeres from libstdc++ This is fix for the Valgrind side. Fix for libstdc++ from

[valgrind] [Bug 345307] Warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-24 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Summary|Please suppress warning |Warning about "still |about "stil

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-24 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Ever confirmed|0 |1 Severity|minor |n

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-21 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #6 from Ivo Raisr --- Created attachment 97339 --> https://bugs.kde.org/attachment.cgi?id=97339&action=edit patch for Solaris -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-21 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added Version|3.10.0 |3.12 SVN --- Comment #5 from Ivo Raisr --- Attache

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-20 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 --- Comment #4 from Ivo Raisr --- I hit this also on Solaris 12 which now ships gcc 5.3. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 345307] Please suppress warning about "still reachable" memory when using libstdc++ from gcc 5

2016-02-20 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=345307 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are receiving this mail bec

[valgrind] [Bug 359133] m_deduppoolalloc.c:258 (vgPlain_allocEltDedupPA): Assertion 'eltSzB <= ddpa->poolSzB' failed.

2016-02-14 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=359133 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #3 from Ivo Raisr ---

[valgrind] [Bug 357871] pthread_spin_destroy not properly wrapped

2016-01-28 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357871 Ivo Raisr changed: What|Removed |Added Assignee|jsew...@acm.org |iv...@ivosh.net -- You are receiving this mail bec

[valgrind] [Bug 357833] Valgrind is broken on recent linux kernel

2016-01-20 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357833 --- Comment #7 from Ivo Raisr --- Hi Mark, Thank you for providing the fix also for Solaris. It works ok on Solaris 12, regression tests passed. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 357871] pthread_spin_destroy not properly wrapped

2016-01-12 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357871 --- Comment #4 from Ivo Raisr --- Fixed in SVN r15756. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 357871] pthread_spin_destroy not properly wrapped

2016-01-12 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357871 --- Comment #5 from Ivo Raisr --- Thank you for the patch and provided test case. I. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 357871] pthread_spin_destroy not properly wrapped

2016-01-11 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357871 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net --- Comment #1 from Ivo Raisr ---

[valgrind] [Bug 357833] Valgrind is broken on recent linux kernel

2016-01-11 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=357833 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are receiving this mail bec

[valgrind] [Bug 92036] A wish for ANSI Colors in the output of valgrind

2016-01-03 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=92036 Ivo Raisr changed: What|Removed |Added CC||iv...@ivosh.net -- You are receiving this mail beca

[valgrind] [Bug 356273] conserve memory by merging adjacent DiLoc entries in the debug info location table

2015-12-12 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356273 --- Comment #4 from Ivo Raisr --- Forgot to say that /bin/true + dependent libraries were compiled by Solaris Studio 12.4, not by gcc. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 356273] conserve memory by merging adjacent DiLoc entries in the debug info location table

2015-12-12 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356273 --- Comment #3 from Ivo Raisr --- Created attachment 96021 --> https://bugs.kde.org/attachment.cgi?id=96021&action=edit log file -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 356273] conserve memory by merging adjacent DiLoc entries in the debug info location table

2015-12-12 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356273 --- Comment #2 from Ivo Raisr --- I tried the patch and I see quite a lot of merged entries on Solaris 12: ... addLoc merging previous: addr 0x7ffd0130c, size 18, line 343, current: addr 0x7ffd0131e, size 28, line 343. ... For simple /bin/true, I see

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-12-04 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 --- Comment #11 from Ivo Raisr --- See also: Bug 356273 - conserve memory by merging adjacent DiLoc entries in the debug info location table -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 356273] New: conserve memory by merging adjacent DiLoc entries in the debug info location table

2015-12-04 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356273 Bug ID: 356273 Summary: conserve memory by merging adjacent DiLoc entries in the debug info location table Product: valgrind Version: unspecified Platform: Compiled Sources

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-12-04 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 Ivo Raisr changed: What|Removed |Added Resolution|--- |FIXED Status|UNCONFIRMED

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-12-04 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 --- Comment #9 from Ivo Raisr --- Yes, '&&' seems misplaced. I attached another patch which fixes this style issues. As regards possible additional merges in canonicaliseLoctab() - preliminary investigation shows that some gains are possible. However I

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-12-04 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 Ivo Raisr changed: What|Removed |Added Attachment #95828|0 |1 is obsolete||

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-11-30 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 Ivo Raisr changed: What|Removed |Added Attachment #95792|0 |1 is obsolete||

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-11-30 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 --- Comment #5 from Ivo Raisr --- As for the memory increase, current functionality does not merge location entries for adjacent addresses. I will enhance the patch to merge entries for adjacent addresses and the same line - this should give us signific

[valgrind] [Bug 356044] Dwarf line info reader misinterprets is_stmt register

2015-11-30 Thread Ivo Raisr via KDE Bugzilla
https://bugs.kde.org/show_bug.cgi?id=356044 --- Comment #4 from Ivo Raisr --- So I spotted the problem by a chance, because another redirected function got used on Solaris/x86+amd64 (using gcc 4.8.2). However this is a generic problem with location info on Linux as well. Consider the following d

<    1   2