A program error generated an exception (such as divide by zero, or a bus or address error) to which only the default exception handler has been attached.
The task that was executing when the exception occurred makes a transition to the suspended state, and a context switch occurs. If an ISR was executing when the exception occurred, the system reboots.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 3.749262 |
|||||||||||||||||||
Context : tLogTask (0x3a468c) |
|||||||||||||||||||
exception (60) |
|||||||||||||||||||
vector : 0x5 |
|||||||||||||||||||
|
|||||||||||||||||||
A hardware interrupt occurred for which there is an associated ISR. Interrupts not connected to the associated ISR by the intConnect( ) routine are not instrumented.
If the interrupt occurs in the context of an executing task, the task is displayed as making a transition to the ready state when the ISR starts executing.
VxWorks routines called from an ISR may be deferred to the interrupted context, if the interrupted context was doing kernel work at the time it was interrupted.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.669146 |
|||||||||||||||||||
Context : INT 3 (0x3) |
|||||||||||||||||||
intEnt-3 (105) |
|||||||||||||||||||
|
|||||||||||||||||||
|
NOTE: The display of this icon is suppressed by default; to display it, toggle the Interrupts button in the Filter Events/State dialog box.
|
||||||||||||||||||
When this ISR finishes executing, control returns to the interrupted context. If the interrupted context was a task, then the highest-priority ready task makes a transition to the executing state.
VxWorks routines called from an ISR may be deferred to the interrupted context, if the interrupted context was doing kernel work at the time it was interrupted.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.671482 |
|||||||||||||||||||
Context : INT 5 (0x5) |
|||||||||||||||||||
intExit (101) |
|||||||||||||||||||
|
|||||||||||||||||||
|
NOTE: The display of this icon is suppressed by default; to display it, toggle the Interrupts button in the Filter Events/State dialog box.
|
||||||||||||||||||
System or application code called the malloc( ), calloc( ), valloc( ), memAlign( ), memPartAlloc( ), or memPartAlignedAlloc( )routine.
System or application code called the msgQDelete( ) routine.
System code uses message queues for the following reasons (for information on TFTP, the exception task, and the logging task, see the VxWorks Programmer's Guide):
Any tasks pending on the message queue make a transition to the ready state. If one of the tasks is the highest-priority ready task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.011881 |
|||||||||||||||||||
Context : task3 (0x3d0218) |
|||||||||||||||||||
msgQDelete (10021) |
|||||||||||||||||||
msgQId : 0x3e03a8 |
|||||||||||||||||||
|
|||||||||||||||||||
System or application code called the msgQReceive( ) routine.
System code uses message queues for the following reasons (for information on TFTP, the exception task, the logging task, and pipes, see the VxWorks Programmer's Guide):
If no message is available in the specified message queue, the task makes a transition to the pended state and a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 4.6377312 |
|||||||||||||||||||
Context : task3 (0x3e0218) |
|||||||||||||||||||
msgQReceive (10022) |
|||||||||||||||||||
timeout : WAIT_FOREVER |
|||||||||||||||||||
bufSize : 20 |
|||||||||||||||||||
buffer : 0xffe770 |
|||||||||||||||||||
msgQId : 0x3e03a8 |
|||||||||||||||||||
|
|||||||||||||||||||
System code, application code, or an ISR called the msgQSend( ) routine.
System code uses message queues for the following reasons (for information on TFTP, the exception task, the logging task, and pipes, see the VxWorks Programmer's Guide):
If tasks are pended on the message queue, the first task that called msgQReceive( ) or the highest-priority task (depending on the message queue creation option) makes a transition to the ready state. If it is the highest-priority task in the system, a context switch occurs.
If the message queue is full, and the sending task has specified a timeout, then it makes a transition to the pended state and a context switch occurs. (ISRs must specify NO_WAIT as the timeout value.)
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 4.6366938 |
|||||||||||||||||||
Context : t2 (0x3dd918) |
|||||||||||||||||||
msgQSend (10023) |
|||||||||||||||||||
priority : MSG_PRI_NORMAL |
|||||||||||||||||||
timeout : WAIT_FOREVER |
|||||||||||||||||||
bufSize : 28 |
|||||||||||||||||||
buffer : 0xf9ca5c |
|||||||||||||||||||
msgQId : 0x3e03a8 |
|||||||||||||||||||
|
|||||||||||||||||||
System or application code called the semDelete( ) routine. (System code issues this routine from the TFTP library only.)
The following system tasks create and use mutex semaphores (for information on these facilities, see the VxWorks Programmer's Guide):
In addition, system code creates and uses these mutex semaphores:
Tasks pending on the semaphore make a transition to the ready state. If one of the unblocked tasks is the highest-priority ready task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.033731 |
|||||||||||||||||||
Context : tLogTask (0x3a3964) |
|||||||||||||||||||
semDelete (10010) |
|||||||||||||||||||
semId : 0x3a0fa4 |
|||||||||||||||||||
|
|||||||||||||||||||
System code, application code, or an ISR called the semFlush( ) routine. (System code only issues this routine from the TFTP library.)
Tasks pending on the semaphore make a transition to the ready state. If one of the unblocked tasks is the highest-priority ready task in the system, a context switch occurs. Note that the semFlush( ) routine is illegal for mutual exclusion semaphores.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.033633 |
|||||||||||||||||||
Context : tLogTask (0x3a3964) |
|||||||||||||||||||
semFlush (10011) |
|||||||||||||||||||
semId : 0x3a0f54 |
|||||||||||||||||||
|
|||||||||||||||||||
|
CAUTION: At AIL level, a semaphore flush stores in the event log not only the semFlush event itself, but also a semGive for every task that was pended on the semaphore. At TST level, only the semFlush event appears.
|
||||||||||||||||||
System code, application code, or an ISR called the semGive( ) routine. (An ISR cannot give a mutual exclusion semaphore.)
WindView system code creates and uses a binary semaphore to manage the target event buffer.
The following system tasks create and use mutex semaphores (for information on these facilities, see the VxWorks Programmer's Guide):
In addition, system code creates and uses these mutex semaphores:
For binary semaphores, if tasks are pended on the semaphore, the first task that called semTake( ) or the highest-priority task (depending on the semaphore create option) makes a transition to the ready state. If it is the highest-priority task in the system, a context switch occurs. If there are no tasks pending on the semaphore, the semaphore becomes full (no effect on task state).
For counting semaphores, if tasks are pended on the semaphore, the first task that called semTake( ) or the highest-priority task (depending on the semaphore create option) makes a transition to the ready state. If it is the highest-priority task in the system, a context switch occurs. If there are no tasks pending on the semaphore, the count of the semaphore is incremented (no effect on task state).
For mutual exclusion semaphores, if the number of gives equals the number of takes, the first task that called semTake( ) or the highest-priority task (depending on the semaphore create option) makes a transition to the ready state. If it is the highest-priority task in the system, a context switch occurs. Otherwise, the semaphore count is decremented (no effect on task state).
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.014918 |
|||||||||||||||||||
Context : t2 (0x3dd918) |
|||||||||||||||||||
semGive (10012) |
|||||||||||||||||||
recurse : 0 |
|||||||||||||||||||
semValue : 0x33dd918 |
|||||||||||||||||||
semId : 0x3a0f54 |
|||||||||||||||||||
|
|||||||||||||||||||
Application code called the semMGiveForce( ) routine. This routine is intended as a debugging aid only; see the VxWorks 5.1 Reference Manual.
If tasks are pended on the mutex semaphore, the first task that called semTake( ) or the highest-priority task (depending on the semaphore create option) makes a transition to the ready state. If it is the highest-priority task in the system, a context switch occurs. If there are no tasks pending on the semaphore, the semaphore becomes full (no effect on task state).
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.011881 |
|||||||||||||||||||
Context : t4 (0x3a6588) |
|||||||||||||||||||
semMGiveForce (10014) |
|||||||||||||||||||
semValue : 0 |
|||||||||||||||||||
semOptions : SEM_Q_PRIORITY |
|||||||||||||||||||
semId : 0x5dafc |
|||||||||||||||||||
|
|||||||||||||||||||
System or application code called the semTake( ) routine.
WindView system code creates and uses a binary semaphore to manage the target event buffer.
The following system tasks create and use mutex semaphores (for information on these facilities, see the VxWorks Programmer's Guide):
In addition, system code creates and uses these mutex semaphores:
For binary semaphores, if the semaphore is full, it is made empty and the task continues executing (no effect on task state). If the semaphore is empty, the task pends on the semaphore, causing a context switch.
For counting semaphores, if the semaphore value is non-zero, it is decremented and the task continues executing (no effect on task state). If the semaphore value is zero, the task pends on the semaphore, causing a context switch.
For mutual exclusion semaphores, if the number of takes exceeds the number of gives, the task continues executing (no effect on task state). Otherwise, the task pends on the semaphore, causing a context switch.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.042625 |
|||||||||||||||||||
Context : t4 (0x3a6588) |
|||||||||||||||||||
semTake (10015) |
|||||||||||||||||||
recurse : 0 |
|||||||||||||||||||
semValue : 0 |
|||||||||||||||||||
semId : 0x3a0804 |
|||||||||||||||||||
|
|||||||||||||||||||
The task being signaled immediately suspends its current thread of execution and invokes the signal handler associated with this signal. (Note that the signal handler is invoked in the context of the task, even if the task is not in the ready state.) Depending on the actions of the signal handler, a context switch can occur.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.1530 |
|||||||||||||||||||
Context : t2 (0x3dd918) |
|||||||||||||||||||
kill (10027) |
|||||||||||||||||||
taskId : 0xf90f6c |
|||||||||||||||||||
signo : 0x1e |
|||||||||||||||||||
|
|||||||||||||||||||
The currently executing task makes a transition to the suspended state, and a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.011881 |
|||||||||||||||||||
Context : tLogTask (0xfa0dc0) |
|||||||||||||||||||
pause (10026) |
|||||||||||||||||||
taskId : 0x39d830 |
|||||||||||||||||||
|
|||||||||||||||||||
The currently executing task makes a transition to the suspended state, and a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.011881 |
|||||||||||||||||||
Context : t2 (0x3dd918) |
|||||||||||||||||||
sigsuspend ( 10025) |
|||||||||||||||||||
sigset : 0x40000000 |
|||||||||||||||||||
|
|||||||||||||||||||
The signalled task is interrupted and the signal handler runs in that task's context.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.00195 |
|||||||||||||||||||
Context : t4 (0xf90f6c) |
|||||||||||||||||||
sigwrapper (10029) |
|||||||||||||||||||
signo : 0xf90f6c |
|||||||||||||||||||
taskId : 0x3dd918 |
|||||||||||||||||||
|
|||||||||||||||||||
For Possible Cause 1, the currently executing task makes a transition to the pended state, and a context switch occurs.
For Possible Cause 2, the pended task makes a transition to the ready state. If it is the highest-priority ready task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.6565 |
|||||||||||||||||||
Context : taskTest (0xf9664c) |
|||||||||||||||||||
safePend (10028) |
|||||||||||||||||||
taskId : 0xf9b5fc |
|||||||||||||||||||
|
|||||||||||||||||||
In system code, the taskDelay( ) routine is used for synchronization purposes, especially in networking code and for shared memory objects.
The currently executing task makes a transition to the delayed state, and a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 3.99884 |
|||||||||||||||||||
Context : t14 (0x38bd08) |
|||||||||||||||||||
taskDelay (10002) |
|||||||||||||||||||
delay : 60 |
|||||||||||||||||||
|
|||||||||||||||||||
If the routine is successful, the specified task makes a transition from its previous state to the dead state. If the executing task deletes itself, a context switch occurs. However, if the specified task is safe from deletion, the calling task makes a transition to the pended state (see the safePend event) until the task is made unsafe by the appropriate number of taskUnsafe( ) routines (or until it releases the mutex semaphore that kept it safe).
Note that once a task is deleted, its task ID may be reused by tasks initialized after its deletion.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.09537 |
|||||||||||||||||||
Context : tLogTask (0x3a468c) |
|||||||||||||||||||
taskDelete (10001) |
|||||||||||||||||||
safeCnt : 1 |
|||||||||||||||||||
taskId : 0x38bd08 |
|||||||||||||||||||
|
|||||||||||||||||||
If the affected task becomes the highest-priority ready task in the system, a context switch occurs. Or, if the calling task lowers its own priority so that it is no longer the highest-priority ready task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.024345 |
|||||||||||||||||||
Context : tLogTask (0x39bf18) |
|||||||||||||||||||
taskPrioritySet (10003) |
|||||||||||||||||||
priority : 100 |
|||||||||||||||||||
priority : 120 |
|||||||||||||||||||
taskId : 0x38bca4 |
|||||||||||||||||||
|
|||||||||||||||||||
The suspended task makes a transition to the ready state. If it is the highest-priority ready task in the system, a context switch occurs.
Note that a task that was in a state other than executing or ready before it was suspended is returned to that state. For example, a delayed task that was suspended is now once again delayed, unless the timeout period has also expired.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.014816 |
|||||||||||||||||||
Context : tLogTask (0x39bf18) |
|||||||||||||||||||
taskResume (10005) |
|||||||||||||||||||
priority : 120 |
|||||||||||||||||||
taskId : 0x381d44 |
|||||||||||||||||||
|
|||||||||||||||||||
No immediate effect. However, see safePend.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.298828 |
|||||||||||||||||||
Context : tLogTask (0x3a468c) |
|||||||||||||||||||
taskSafe (10006) |
|||||||||||||||||||
safeCnt : 1 |
|||||||||||||||||||
taskId : 0x3a468c |
|||||||||||||||||||
|
|||||||||||||||||||
The new task makes a transition from the nonexistent state to the suspended state. When the new task is activated (resumed), if it is the highest-priority task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.27065 |
|||||||||||||||||||
Context : tLogTask (0x3a468c) |
|||||||||||||||||||
taskSpawn (10000) |
|||||||||||||||||||
options : VX_FP_TASK VX_STDIO |
|||||||||||||||||||
entry : 0x328a4 |
|||||||||||||||||||
stackSize: 0x2710 |
|||||||||||||||||||
priority : 0x63 |
|||||||||||||||||||
taskId : 0x390ac0 |
|||||||||||||||||||
|
|||||||||||||||||||
The task makes a transition to the suspended state. If the calling task suspends itself, a context switch occurs.
Note that if a task was in a state other than executing or ready before it was suspended, it is still in that state. For example, a delayed task that is suspended is now delayed and suspended.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 2.445541 |
|||||||||||||||||||
Context : tLogTask (0x3a468c) |
|||||||||||||||||||
taskSuspend (10004) |
|||||||||||||||||||
taskId : 0x38bd08 |
|||||||||||||||||||
|
|||||||||||||||||||
If this taskUnsafe( ) routine released the last safe-from-deletion lock on the specified task, then any tasks in the pended state because they are waiting to delete this task are put into the ready state (see the safePend event). As soon as one of those tasks executes, the specified task is deleted; therefore, it makes a transition from its previous state to the dead state.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.299007 |
|||||||||||||||||||
Context : tLogTask (0x3a468c) |
|||||||||||||||||||
taskUnsafe (10007) |
|||||||||||||||||||
safeCnt : 2 |
|||||||||||||||||||
taskId : 0x3a468c |
|||||||||||||||||||
|
|||||||||||||||||||
The task makes a transition from the pended state to the ready state. If it is the highest-priority ready task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.433154 |
|||||||||||||||||||
Context : INT 6 (0x6) |
|||||||||||||||||||
tick : timeout (631) |
|||||||||||||||||||
taskId : 0x390fa4 |
|||||||||||||||||||
|
|||||||||||||||||||
Round-robin scheduling was enabled with the kernelTimeSlice( ) routine, and a time slice has expired.
If the currently executing task has the same priority as one or more other tasks, it makes a transition to the ready state, and the next task of the same priority executes. That is, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 1.533078 |
|||||||||||||||||||
Context : INT 6 (0x6) |
|||||||||||||||||||
tick : timeslice (607) |
|||||||||||||||||||
|
|||||||||||||||||||
The task makes a transition from the delayed state to the ready state. If it is the highest-priority ready task in the system, a context switch occurs.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 0.483216 |
|||||||||||||||||||
Context : INT 6 (0x6) |
|||||||||||||||||||
tick : undelay (618) |
|||||||||||||||||||
taskId : 0x390fa4 |
|||||||||||||||||||
|
|||||||||||||||||||
Because the watchdog timer routine is called from interrupt level, the current context is interrupted. If the current context is a task, the task is displayed as making a transition to the ready state.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 2.149721 |
|||||||||||||||||||
Context : INT 6 (0x6) |
|||||||||||||||||||
tick : watchdog (608) |
|||||||||||||||||||
wdId : 0x3d6180 |
|||||||||||||||||||
|
|||||||||||||||||||
Other information is collected based on your coding of these routines. For information, see F.4 Creating Icons for User-Defined Events.
|
|||||||||||||||||||
|
|||||||||||||||||||
Time : 9.672774 |
|||||||||||||||||||
Context : t1 (0x3a118c) |
|||||||||||||||||||
User event 2 |
|||||||||||||||||||
Address : 0x1a644 |
|||||||||||||||||||
|
|||||||||||||||||||
|
NOTE: The icon shown above is the WRS-supplied, default user event icon. You can design your own, if you wish; see the manual for details. F.4 Creating Icons for User-Defined Events
|
||||||||||||||||||