INtime® 3.1 Software - tenAsys

INtime 3.1 Software
You can now run your INtime application and observe the CPU usage of both the
Windows and RT kernels. When viewing the CPU usage, keep in mind that the
Performance Monitor displays total CPU usage which includes more than the activity
generated by an INtime application.
Status messages
When the RT kernel is running, a protection fault which occurs in the RT portion of an
INtime application is handled by the default system hardware exception handler
which suspends the faulting thread. Such threads display in the INtime Explorer with
the state ‘suspended because of an exception’. For threads in this state, the CPU
frame displays the thread’s CPU context when the hardware fault occurred, including
the CS:EIP address of the faulting instruction.
The error code indicates the fault encountered as follows:
Fault Code Description
EH_ZERO_DIVIDE 0x8100 Divide by Zero error
EH_SINGLE_STEP 0x8101 Single Step
EH_NMI 0x8102 NMI
EH_DEBUG_TRAP 0x8103 Debug Interrupt (Ignored by handler)
EH_OVERFLOW 0x8104 Overflow error
EH_ARRAY_BOUNDS 0x8105 Array Bounds error
EH_INVALID_OPCODE 0x8106 Invalid Opcode error
EH_DEVICE_NOT_PRESENT 0x8107 NPX device not present
EH_DOUBLE_FAULT 0x8108 Double Fault error
EH_DEVICE_ERROR 0x8109 NPX device error
EH_INVALID_TSS 0x810A Invalid TSS error
EH_SEGMENT_NOT_PRESENT 0x810B Segment Not Present error
EH_STACK_FAULT 0x810C Stack Fault
EH_GENERAL_PROTECTION 0x810D General Protection Fault
EH_PAGE_FAULT 0x810E Page Fault
If a debugger is running when the protection fault occurs, the debugger traps the fault
and allows you to debug or delete the offending program.
Prepare for release
Before you begin
• On the target system, ensure that you are logged on with Administrator privileges.
• Exit all programs prior to installing INtime software.
102