Red Hat Bugzilla – Bug 1265566
sigpending syscall not implemented on aarch64
Last modified: 2016-11-03 22:55:10 EDT
Description of problem:
int main(int argc, char **argv)
==9121== Copyright (C) 2002-2013, and GNU GPL'd, by Julian Seward et al.
==9121== Using Valgrind-3.10.0 and LibVEX; rerun with -h for copyright info
==9121== Command: /tmp/tmp.JXCBD0Zctt/sigpending
==9121== Parent PID: 8291
--9121-- WARNING: unhandled syscall: 136
--9121-- You may be able to write your own handler.
--9121-- Read the file README_MISSING_SYSCALL_OR_IOCTL.
--9121-- Nevertheless we consider this a bug. Please report
--9121-- it at http://valgrind.org/support/bug_reports.html.
==9121== HEAP SUMMARY:
==9121== in use at exit: 0 bytes in 0 blocks
==9121== total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==9121== All heap blocks were freed -- no leaks are possible
==9121== For counts of detected and suppressed errors, rerun with: -v
==9121== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
This was revealed by running a reproducer for https://bugzilla.redhat.com/show_bug.cgi?id=1225964 - which was reported against ppc64. I can't see qemu - which was mentioned as an example of apps that are limited by this on pp64 - available for aarch64 though.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Fixed by in valgrind svn r15676
The upstream patch mentioned in comment #1 can be backported.
QA note: sigpending syscall support (or rt_sigpending, since aarch64 does not have sigpending) is covered by valgrind's ./memcheck/tests/arm64-linux/scalar.c test.
Verified for build valgrind-3.11.0-22.el7.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.