https://bugs.kde.org/show_bug.cgi?id=359503
Mark Wielaard <m...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |m...@redhat.com
--- Comment #6 from Mark Wielaard <m...@redhat.com> ---
Created attachment 97762
--> https://bugs.kde.org/attachment.cgi?id=97762&action=edit
Use correct syscall numbers on arm64
While testing some of these newly hooked system calls I noticed that valgrind
uses some wrong system call numbers on arm64. This also affects our own dup2
and rename implementations (arm64 only has dup3 and renameat). Which causes
callgrind to sometimes be unable to rename dump files on arm64.
Fixed the syscall numbers using the overview given by Marcin:
https://marcin.juszkiewicz.com.pl/2016/03/05/from-a-diary-of-aarch64-porter-system-calls/
--
You are receiving this mail because:
You are watching all bug changes.
