[valgrind] [Bug 415621] epoll_ctl reports for uninitialized padding

2020-07-05 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=415621 Mark Wielaard changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED

[valgrind] [Bug 415621] epoll_ctl reports for uninitialized padding

2020-01-08 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=415621 zbys...@in.waw.pl changed: What|Removed |Added CC||zbys...@in.waw.pl -- You are receiving this

[valgrind] [Bug 415621] epoll_ctl reports for uninitialized padding

2019-12-28 Thread Simon Richter
https://bugs.kde.org/show_bug.cgi?id=415621 --- Comment #2 from Simon Richter --- Not yet, I'd need guidance on what would be the desired behaviour for uninitialized padding in the middle of a struct (which is harmless but might leak data if it is blindly copied around). Is there a flag for hidi

[valgrind] [Bug 415621] epoll_ctl reports for uninitialized padding

2019-12-28 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=415621 --- Comment #1 from Julian Seward --- Do you have a syscall wrapper patch that fixes this, by any chance? -- You are receiving this mail because: You are watching all bug changes.