[valgrind] [Bug 379966] New: WARNING: unhandled syscall: 313

2017-05-18 Thread Bartosz Golaszewski
https://bugs.kde.org/show_bug.cgi?id=379966 Bug ID: 379966 Summary: WARNING: unhandled syscall: 313 Product: valgrind Version: unspecified Platform: Debian stable OS: Linux Status: UNCONFIRMED Severity: mi

[valgrind] [Bug 379966] WARNING: unhandled syscall: 313

2017-05-18 Thread Bartosz Golaszewski
https://bugs.kde.org/show_bug.cgi?id=379966 Bartosz Golaszewski changed: What|Removed |Added CC||bartekg...@gmail.com Version

[valgrind] [Bug 379966] WARNING: unhandled syscall: 313

2017-05-18 Thread Bartosz Golaszewski
https://bugs.kde.org/show_bug.cgi?id=379966 Bartosz Golaszewski changed: What|Removed |Added Latest Commit||r16395 -- You are receiving this mail

[valgrind] [Bug 379966] WARNING: unhandled syscall: 313 (finit_module)

2017-05-18 Thread Bartosz Golaszewski
https://bugs.kde.org/show_bug.cgi?id=379966 --- Comment #2 from Bartosz Golaszewski --- Right, I checked the wrong file. It's in /usr/include/x86_64-linux-gnu/asm/unistd_64.h on Debian. I'll try to create a wrapper for this syscall. -- You are receiving this mail because: You are wa

[valgrind] [Bug 379966] WARNING: unhandled amd64-linux syscall: 313 (finit_module)

2017-05-18 Thread Bartosz Golaszewski
https://bugs.kde.org/show_bug.cgi?id=379966 --- Comment #4 from Bartosz Golaszewski --- Hmm... it's already there in ./coregrind/m_syswrap/syswrap-amd64-linux.c but it's commented out: 835 // LIN__(__NR_finit_module, sys_ni_syscall), // 313 Does it mean that it just does

[valgrind] [Bug 379966] WARNING: unhandled amd64-linux syscall: 313 (finit_module)

2017-05-19 Thread Bartosz Golaszewski
https://bugs.kde.org/show_bug.cgi?id=379966 --- Comment #6 from Bartosz Golaszewski --- Created attachment 105623 --> https://bugs.kde.org/attachment.cgi?id=105623&action=edit add wrapper for finit_module() There was no wrapper - only the basic definitions. I wrote the wrapper and i