Bug 356676

Summary: Unhandled arm64-linux syscalls: 125 and 126 (sched_get_priority_max/min)
Product: [Developer tools] valgrind Reporter: Роман Донченко <dpb>
Component: generalAssignee: Julian Seward <jseward>
Status: RESOLVED FIXED    
Severity: normal CC: marcin
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:

Description Роман Донченко 2015-12-14 12:09:28 UTC
$ valgrind --version
valgrind-3.11.0

$ uname -p
aarch64

$ cat test.c
#include <sched.h>

int main() {
  sched_get_priority_max(SCHED_RR);
  sched_get_priority_min(SCHED_RR);
}

$ gcc test.c

$ valgrind ./a.out
==10657== Memcheck, a memory error detector
==10657== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==10657== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==10657== Command: ./a.out
==10657== 
--10657-- WARNING: unhandled arm64-linux syscall: 125
--10657-- You may be able to write your own handler.
--10657-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--10657-- Nevertheless we consider this a bug.  Please report
--10657-- it at http://valgrind.org/support/bug_reports.html.
--10657-- WARNING: unhandled arm64-linux syscall: 126
--10657-- You may be able to write your own handler.
--10657-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--10657-- Nevertheless we consider this a bug.  Please report
--10657-- it at http://valgrind.org/support/bug_reports.html.
==10657== 
==10657== HEAP SUMMARY:
==10657==     in use at exit: 0 bytes in 0 blocks
==10657==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==10657== 
==10657== All heap blocks were freed -- no leaks are possible
==10657== 
==10657== For counts of detected and suppressed errors, rerun with: -v
==10657== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)


Reproducible: Always
Comment 1 Marcin Juszkiewicz 2016-02-17 14:58:22 UTC
patch from https://bugs.kde.org/show_bug.cgi?id=359503 handles it
Comment 2 Julian Seward 2016-09-13 16:40:00 UTC
Fixed by bug 359503.