Bug 369028 - WARNING: unhandled amd64-linux syscall: 314 (sched_setattr)
Summary: WARNING: unhandled amd64-linux syscall: 314 (sched_setattr)
Status: RESOLVED DUPLICATE of bug 369029
Alias: None
Product: valgrind
Classification: Developer tools
Component: general (show other bugs)
Version: 3.11.0
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Julian Seward
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-19 06:45 UTC by Marcin Juszkiewicz
Modified: 2021-10-04 09:01 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Marcin Juszkiewicz 2016-09-19 06:45:48 UTC 
<<<test_start>>>
tag=sched_setattr01_valgrind_memory_leak_check stime=1474195092
cmdline=" valgrind -q --leak-check=full --trace-children=yes sched_setattr01"
contacts=""
analysis=exit
<<<test_output>>>
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
--24029-- WARNING: unhandled amd64-linux syscall: 314
--24029-- You may be able to write your own handler.
--24029-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--24029-- Nevertheless we consider this a bug.  Please report
--24029-- it at http://valgrind.org/support/bug_reports.html.
sched_setattr01    1  TFAIL  :  sched_setattr01.c:96: sched_setattr(0,attr,0) returned: -1 expected: 0: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr01    2  TFAIL  :  sched_setattr01.c:109: sched_setattr(32768,attr,0): expected: 3 - ESRCH: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr01    3  TFAIL  :  sched_setattr01.c:109: sched_setattr(0,attr,0): expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not implemented
sched_setattr01    4  TFAIL  :  sched_setattr01.c:109: sched_setattr(0,attr,1000): expected: 22 - EINVAL: TEST_ERRNO=ENOSYS(38): Function not implemented
<<<execution_status>>>
initiation_status="ok"
duration=1 termination_type=exited termination_id=1 corefile=no
cutime=74 cstime=2
<<<test_end>>>


Reproducible: Always
Comment 1 Marcin Juszkiewicz 2018-04-30 08:03:15 UTC 
Can we close it? IIRC it was merged into valgrind.
Comment 2 Tom Hughes 2018-04-30 09:57:19 UTC 
I see no sign that this has been added.
Comment 3 zephyrus00jp 2020-04-14 23:29:50 UTC 
Hi,
I uploaded a patch to support sched_setattr (and sched_getattr) in bug 369029.

https://bugs.kde.org/show_bug.cgi?id=369029

Can someone take a look?

TIA
Comment 4 Mark Wielaard 2021-10-04 09:01:32 UTC 

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