On Fri, Jul 28, 2017 at 08:33:57AM +0300, Edgar Kaziakhmedov wrote: [...] > Actually, I am not quite sure about ARM architectures, am I right there or > not. (I mean > ABI modes). Because, according to the current syscallent.h file in arm dir, > there is not support > for subcall in ARM EABI, is it correct? Because, in the kernel there is place > for these subcalls.
That's simple. If you have a look at the kernel, you'll see the following: $ grep -Fw oabi arch/arm/tools/syscall.tbl # <num> <abi> <name> [<entry point> [<oabi compat entry point>]] # common - for system calls shared between oabi and eabi (may have compat) # oabi - for oabi-only system calls (may have compat) # For each syscall number, "common" is mutually exclusive with oabi and eabi 13 oabi time sys_time 22 oabi umount sys_oldumount 25 oabi stime sys_stime 27 oabi alarm sys_alarm 30 oabi utime sys_utime 76 oabi getrlimit sys_old_getrlimit 82 oabi select sys_old_select 89 oabi readdir sys_old_readdir 90 oabi mmap sys_old_mmap 102 oabi socketcall sys_socketcall sys_oabi_socketcall 113 oabi syscall sys_syscall 117 oabi ipc sys_ipc sys_oabi_ipc In other words, socketcall and ipc are implemented for oabi only, on eabi they return ENOSYS. -- ldv
signature.asc
Description: PGP signature
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________ Strace-devel mailing list Strace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/strace-devel
