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

https://bugs.kde.org/show_bug.cgi?id=357833 Mark Wielaard changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

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

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 357833] Valgrind is broken on recent linux kernel

https://bugs.kde.org/show_bug.cgi?id=357833 Mark Wielaard changed: What|Removed |Added CC||m...@redhat.com --- Comment

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

https://bugs.kde.org/show_bug.cgi?id=357833 --- Comment #4 from Mark Wielaard --- Replicated it now with the fedora rawhide kernel 4.5.0-0.rc0.git6.1.fc24.i686+PAE Not setting the RLIMIT_DATA to zero in coregrind/m_main.c (valgrind_main) does indeed work around it. -- You are

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

https://bugs.kde.org/show_bug.cgi?id=357833 --- Comment #6 from Mark Wielaard --- Created attachment 96751 --> https://bugs.kde.org/attachment.cgi?id=96751=edit Remove setting zero RLIMIT_DATA The simplest seems to be to just remove the zero data rlimit. It also gets rid of

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

https://bugs.kde.org/show_bug.cgi?id=357833 --- Comment #5 from Mark Wielaard --- For reference here is the full commit explaining that previously the RLIMIT_DATA value indeed was mostly harmless only affecting brk, but now restricts any data area allocations: commit

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

https://bugs.kde.org/show_bug.cgi?id=357833 Tom Hughes changed: What|Removed |Added CC||t...@compton.nu --- Comment #1

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

https://bugs.kde.org/show_bug.cgi?id=357833 --- Comment #2 from kmu --- > I presume that this code in coregrind/m_main.c is the issue indeed, after i commented out "VG_(setrlimit)(VKI_RLIMIT_DATA, );" the problem was gone (as i wrote in the description). -- You are