[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2022-01-26 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416753 --- Comment #7 from Mark Wielaard --- *** Bug 447386 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2021-12-22 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416753 Mark Wielaard changed: What|Removed |Added CC||derp...@gmail.com --- Comment #6 from Mark

[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2020-03-04 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416753 Mark Wielaard changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED

[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2020-03-04 Thread Julian Seward
https://bugs.kde.org/show_bug.cgi?id=416753 Julian Seward changed: What|Removed |Added CC||jsew...@acm.org --- Comment #4 from Julian

[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2020-02-29 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416753 Mark Wielaard changed: What|Removed |Added Attachment #126478|0 |1 is obsolete|

[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2020-02-28 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416753 --- Comment #2 from Mark Wielaard --- The patch works, but it does catch some issues with uninitialized fields in the new timespec64 (but that proves it works!). That is because glibc uses its own definition of timespec64: /* The glibc Y2038-proof

[valgrind] [Bug 416753] new 32bit time syscalls for 2038+

2020-02-28 Thread Mark Wielaard
https://bugs.kde.org/show_bug.cgi?id=416753 Mark Wielaard changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0