Bug 422417 - WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)
Summary: WARNING: unhandled amd64-linux syscall: 315 (sched_getattr)
Status: RESOLVED DUPLICATE of bug 369029
Alias: None
Product: valgrind
Classification: Developer tools
Component: memcheck (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-03 13:20 UTC by Norman Goldstein
Modified: 2020-06-03 13:32 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Norman Goldstein 2020-06-03 13:20:29 UTC 
SUMMARY
Running a QT GUI application, get the message:
--24339-- WARNING: unhandled amd64-linux syscall: 315
--24339-- You may be able to write your own handler.
--24339-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24339-- Nevertheless we consider this a bug.  Please report
--24339-- it at http://valgrind.org/support/bug_reports.html.


STEPS TO REPRODUCE
1. Run the QT application (sorry, have not written a minimal application)
2. 
3. 

OBSERVED RESULT
The above message


EXPECTED RESULT
No such message


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma:             Linux Fedora 32 x86-54
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version:                    5.13.2

ADDITIONAL INFORMATION
Comment 1 Norman Goldstein 2020-06-03 13:23:35 UTC 
Forgot to mention the valgrind version:

==24339== Memcheck, a memory error detector
==24339== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
==24339== Using Valgrind-3.16.0 and LibVEX; rerun with -h for copyright info
Comment 2 Mark Wielaard 2020-06-03 13:29:25 UTC 
315 is sched_getattr on amd64
https://www.man7.org/linux/man-pages/man2/sched_getattr.2.html
which indeed hasn't been supported
Comment 3 Mark Wielaard 2020-06-03 13:32:36 UTC 
Seems this was already reported 4 (!) years ago and someone did propose a patch. Time to get this fixed.

*** This bug has been marked as a duplicate of bug 369029 ***