Difference between revisions of "Talk:Kernel Syscalls"

From The iPhone Wiki
Jump to: navigation, search
(about wrong data)
Line 14: Line 14:
 
-- Edit:
 
-- Edit:
   
OOOOOH. Now I get it. He meant the CPU syscalls, not the kernel syscalls. This needs more research (who originally put that part?)
+
OOOOOH. Now I get it. He meant the CPU syscalls, not the kernel syscalls. This needs more research (who originally put that part?) {{unsigned|morpheus|2 Mar 2012 02:04 UTC}}
  +
:Look at page history. It seems like it came from [[User:ChronicDev|Chronic]]? Hardly imaginable he entered wrong infos. Maybe just very outdated? I have too few experience with ARM and kernel to contribute here. Feel free to remove wrong infos or just mention where it belongs to. --[[User:Http|http]] 01:14, 2 March 2012 (MST)

Revision as of 08:14, 2 March 2012

i dont know if its right, pls correct me if im wrong :) --Zmaster 13:58, 29 November 2011 (MST)

HTTP/i0nic: The following is hardly "bogus". 0x30d2ad54 <chown>: mov r12, #16  ; 0x10, being # of chown 0x30d2ad58 <chown+4>: svc 0x00000080 is a direct disassembly of libSystem. You can see that with gdb on a jb device.

SVC is an ARM instruction to invoke a "supervisor call". The 0x80 is the call #, because the chip allows an interrupt vector, much like Intel's INT instruction. Then, you place the syscall # (in the above example, chown) in r12. morpheus ||3/1/2012, 20:01 EST.

-- Edit:

OOOOOH. Now I get it. He meant the CPU syscalls, not the kernel syscalls. This needs more research (who originally put that part?) --The preceding unsigned comment was added by morpheus (talk) 2 Mar 2012 02:04 UTC. Please consult this page for more info on how to sign pages, and how to fix this.

Look at page history. It seems like it came from Chronic? Hardly imaginable he entered wrong infos. Maybe just very outdated? I have too few experience with ARM and kernel to contribute here. Feel free to remove wrong infos or just mention where it belongs to. --http 01:14, 2 March 2012 (MST)