Public bug reported: On 20.04 64 Bit valgrind 3.15 using glibc 2.31 throws warnings on some time related systemcalls, spamming the output and making it unreadable and unusable large.
e.g. --7970-- WARNING: unhandled x86-linux syscall: 407 ==7970== at 0x45765ED: __GI___clock_nanosleep_time64 (clock_nanosleep.c:52) ==7970== by 0x45766D1: clock_nanosleep@@GLIBC_2.17 (clock_nanosleep.c:92) ==7970== by 0x457D153: nanosleep (nanosleep.c:27) ... --7970-- You may be able to write your own handler. --7970-- Read the file README_MISSING_SYSCALL_OR_IOCTL. --7970-- Nevertheless we consider this a bug. Please report --7970-- it at http://valgrind.org/support/bug_reports.html. at every call of usleep. There already is a fix at valgrind git at trunk. Related Bugreport there: https://bugs.kde.org/show_bug.cgi?id=416753 Bugfix commit: https://sourceware.org/git/?p=valgrind.git;a=commit;h=3d6a8157d52f18261f2c1a0888c2cfd3289b371e ** Affects: valgrind (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1877963 Title: Valgrind throws warnings at some time related glibc 2.31 calls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/valgrind/+bug/1877963/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
