sysenter

Syscall or sysenter on 32 bits Linux?

本秂侑毒 提交于 2019-12-04 19:36:49
问题 Since MS‑DOS, I know system invocation using interrupts. In old papers, I saw reference to int 80h to invoke system functions on Linux. Since a rather long time now, I know int 80h is deprecated in favour of the syscall instruction. But I can't get it working on my 32 bits machine. The question Is the syscall instruction to be used on 64 bits platform only? Doesn't 32 bits Linux makes use of syscall ? A sample test On my 32 bits Linux (Ubuntu Precise), this program terminates with a core dump

Syscall or sysenter on 32 bits Linux?

╄→гoц情女王★ 提交于 2019-12-03 13:47:38
Since MS‑DOS, I know system invocation using interrupts. In old papers, I saw reference to int 80h to invoke system functions on Linux. Since a rather long time now, I know int 80h is deprecated in favour of the syscall instruction. But I can't get it working on my 32 bits machine. The question Is the syscall instruction to be used on 64 bits platform only? Doesn't 32 bits Linux makes use of syscall ? A sample test On my 32 bits Linux (Ubuntu Precise), this program terminates with a core dump: global _start _start: mov eax, 4 ; 4 is write mov ebx, 1 ; 1 is stdout mov ecx, message ; address of

CPU raises with attributesOfItemAtPath:error:

☆樱花仙子☆ 提交于 2019-12-01 10:23:36
问题 I am using [NSFileManager attributesOfItemAtPath:error:] function for fetching attributes of file. But sometimes my application cpu is going upto 100%. I am using this function for 100k(approx.) files. Sample of my application: 2128 -[NSFileManager attributesOfItemAtPath:error:] 2128 +[NSFileAttributes _attributesAtPath:partialReturn:filterResourceFork:error:] 2123 _attributesAtPath 2072 listxattr 29 realloc 18 realloc 11 szone_size 22 _attributesAtPath 5 _sysenter_trap Can anyone please help