Home
last modified time | relevance | path

Searched refs:EIP (Results 1 – 13 of 13) sorted by relevance

/linux-2.6.39/arch/um/sys-i386/shared/sysdep/
Dptrace_user.h36 #define REGS_IP_INDEX EIP
39 #define PT_IP_OFFSET PT_OFFSET(EIP)
40 #define PT_IP(regs) ((regs)[EIP])
Dptrace.h107 case EIP: val = UPT_IP(regs); break; \
134 case EIP: UPT_IP(regs) = val; break; \
/linux-2.6.39/arch/x86/include/asm/
Dptrace-abi.h18 #define EIP 12 macro
/linux-2.6.39/arch/um/sys-i386/asm/
Dprocessor.h72 #define KSTK_EIP(tsk) KSTK_REG(tsk, EIP)
/linux-2.6.39/arch/um/os-Linux/sys-i386/
Dregisters.c46 case EIP: in get_thread_reg()
/linux-2.6.39/arch/um/sys-i386/
Duser-offsets.c27 DEFINE(HOST_IP, EIP); in foo()
/linux-2.6.39/Documentation/
DBUG-HUNTING166 > EIP is at ip_queue_xmit+0x14/0x4c0
196 CONFIG_DEBUG_INFO enabled, you can simply copy the EIP value from the
199 EIP: 0060:[<c021e50e>] Not tainted VLI
209 EIP is at vt_ioctl+0xda8/0x1482
Doops-tracing.txt201 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
Dkmemcheck.txt260 The single most valuable information in this report is the RIP (or EIP on 32-
/linux-2.6.39/
DREADME311 EIP: 0010:XXXXXXXX
334 look up what the EIP value means. The hex value as such doesn't help
336 kernel setup. What you should do is take the hex value from the EIP
343 the EIP from the kernel crash, do:
372 with the EIP value.)
/linux-2.6.39/Documentation/zh_CN/
Doops-tracing.txt165 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
/linux-2.6.39/lib/
DKconfig.debug679 of the BUG call as well as the EIP and oops trace. This aids
/linux-2.6.39/Documentation/filesystems/
Dproc.txt293 eip current value of EIP