[valgrind] [Bug 439090] unhandled amd64-linux syscall: 436 (close_range)

2021-10-04 Thread Lubomir Rintel
https://bugs.kde.org/show_bug.cgi?id=439090 Lubomir Rintel changed: What|Removed |Added CC||lkund...@v3.sk --- Comment #4 from Lubomir Rin

[valgrind] [Bug 439090] unhandled amd64-linux syscall: 436 (close_range)

2021-09-16 Thread Olly Betts
https://bugs.kde.org/show_bug.cgi?id=439090 --- Comment #3 from Olly Betts --- glibc 2.34 (released 2021-08-01) added close_range() and closefrom(), both of which make use of the close_range syscall. -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 439090] unhandled amd64-linux syscall: 436 (close_range)

2021-06-29 Thread Paul Wise
https://bugs.kde.org/show_bug.cgi?id=439090 Paul Wise changed: What|Removed |Added CC||pa...@bonedaddy.net -- You are receiving this mail

[valgrind] [Bug 439090] unhandled amd64-linux syscall: 436 (close_range)

2021-06-23 Thread Olly Betts
https://bugs.kde.org/show_bug.cgi?id=439090 --- Comment #2 from Olly Betts --- Created attachment 139634 --> https://bugs.kde.org/attachment.cgi?id=139634&action=edit Work in progress patch -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 439090] unhandled amd64-linux syscall: 436 (close_range)

2021-06-23 Thread Olly Betts
https://bugs.kde.org/show_bug.cgi?id=439090 --- Comment #1 from Olly Betts --- I had a go at implementing support for close_range, but ended up out of my depth. The problem I have no idea how to solve is what to do if log fds fall in the middle of the range of fds which are to be closed - lookin