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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 3.749262		The time at which the event occurred		X		X		X
context		Context : tLogTask (0x3a468c)		The context in which the event occurred		X		X		X
eventName		exception (60)		The name of the event associated with this icon		X		X		X
vector		vector : 0x5		This exception's vector number; number is architecture-dependent		X		X		X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.669146		The time at which the event occurred		X		X		X
context		Context : INT 3 (0x3)		The context in which the event occurred		X		X		X
eventName		intEnt-3 (105)		The name and INT level of the event associated with this icon; the internal event number = 102 + INT level		X		X		X

The ISR finished executing.

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.671482		The time at which the event occurred		X		X		X
context		Context : INT 5 (0x5)		The context in which the event occurred		X		X		X
eventName		intExit (101)		The name of the event associated with this icon		X		X		X

System or application code called the memAddToPool( ) or the memPartAddToPool( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
eventName		memPartAddtoPool (nnnnn)		The name of the event associated with this icon						X
timeStamp		Time : 0.669146		The time at which the event occurred						X
poolSize		poolSize=0x200		Amount of memory added to pool						X
partId		partId=0x80373600		ID of memory partition						X

System or application code called the malloc( ), calloc( ), valloc( ), memAlign( ), memPartAlloc( ), or memPartAlignedAlloc( )routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
eventName		memPartAlignedAlloc (nnnnn)		The name of the event associated with this icon						X
timeStamp		Time : 0.669146		The time at which the event occurred						X
nBytes		nBytes=0x60		Total amount of memory requested						X
nBytesPlusHeaderAlign		nBytesPlusHeaderAlign =0x68		Total amount of memory allocated						X
pBlock		pBlock=0x3bb7290		Pointer to memory block						X
partId		partId=0x198118		ID of memory partition						X

System or application code called the memPartCreate( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
eventName		memPartCreate (nnn)		The name of the event associated with this icon						X
timeStamp		Time : 0.669146		The time at which the event occurred						X
poolSize		poolSize=0x200		Size of pool allocated						X
partId		partId=0x80373600		ID of memory partition						X

System or application code called the free( ), cfree( ), or memPartFree( ), routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
eventName		memPartFree (nnnnn)		The name of the event associated with this icon						X
timeStamp		Time : 0.669146		The time at which the event occurred						X
nBytesPlusHeaderAlign		nBytesPlusHeaderAlign =0x78		Total amount of memory allocated						X
pBlock		pBlock=0x8036e800		Pointer to memory block						X
partId		0x8008f1ec		ID of memory partition						X

System or application code called the realloc( ) or memPartRealloc( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
eventName		memPartRealloc (nnnnn)		The name of the event associated with this icon						X
timeStamp		Time : 0.669146		The time at which the event occurred						X
nBytes		nBytes=0x140		Total amount of memory requested						X
nBytesPlusHeaderAlign		nBytesPlusHeaderAlign =0x1a0		Total amount of memory allocated						X
pBlock		pBlock=0x803736c0		Pointer to memory block						X
partId		partId=0x80373600		ID of memory partition						X

System or application code called the msgQCreate( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.011881		The time at which the event occurred						X
context		Context : t2 (0xf9ace)		The context in which the event occurred						X
eventName		msgQCreate (10020)		The name of the event associated with this icon						X
msgOptions		msgOptions : MSG_Q_FIFO		Message queueing options: MSG_Q_FIFO or MSG_Q_PRIORITY						X
maxMsgLen		maxMsgLen : 0x14		Maximum possible length, in bytes, of each message in this message queue						X
maxMsg		maxMsg : 0xa		Maximum number of messages this message queue can hold						X
msgQId		msgQId : 0xfff2308		ID of the created message queue						X

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):

• The TFTP server uses message queues to manage the pool of available reply descriptors.

• A message queue is created for communication with the exception task (tExcTask).

• A message queue manages the messages to be logged with the logging task (tLogTask).

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.011881		The time at which the event occurred				X		X
context		Context : task3 (0x3d0218)		The context in which the event occurred				X		X
eventName		msgQDelete (10021)		The name of the event associated with this icon				X		X
msgQId		msgQId : 0x3e03a8		ID of the message queue to delete				X		X

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):

• The TFTP server uses message queues to manage the pool of available reply descriptors.

• A message queue is created for communication with the exception task (tExcTask).

• A message queue manages the messages to be logged with the logging task (tLogTask).

• Message queues are used by pipe operations.

If no message is available in the specified message queue, the task makes a transition to the pended state and a context switch occurs.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 4.6377312		The time at which the event occurred				X		X
context		Context : task3 (0x3e0218)		Context in which the event occurred				X		X
eventName		msgQReceive (10022)		The name of the event associated with this icon				X		X
timeout		timeout : WAIT_FOREVER		Number of ticks that the task is to wait (pend) for a message, or NO_WAIT or WAIT_FOREVER						X
bufSize		bufSize : 20		Size of the buffer to receive message						X
buffer		buffer : 0xffe770		Address of buffer to receive message						X
msgQId		msgQId : 0x3e03a8		ID of the message queue from which to receive the message				X		X

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):

• The TFTP server uses message queues to manage the pool of available reply descriptors.

• A message queue is created for communication with the exception task (tExcTask).

• A message queue manages the messages to be logged with the logging task (tLogTask).

• Message queues are used by pipe operations.

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.)

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 4.6366938		The time at which the event occurred				X		X
context		Context : t2 (0x3dd918)		The context in which the event occurred				X		X
eventName		msgQSend (10023)		The name of the event associated with this icon				X		X
msgPriority		priority : MSG_PRI_NORMAL		Priority of the message being sent: MSG_PRI_NORMAL or MSG_PRI_URGENT						X
timeout		timeout : WAIT_FOREVER		Number of ticks that the task is to wait (pend) for free space if the message queue is full, or NO_WAIT, or WAIT_FOREVER						X
bufSize		bufSize : 28		Length of the message to be sent						X
buffer		buffer : 0xf9ca5c		Address of the buffer holding the message to be sent						X
msgQId		msgQId : 0x3e03a8		ID of the message queue to which to send the message				X		X

Application code called the semBCreate( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.033995		The time at which the event occurred						X
context		Context : tLogTask (0x3a3964)		The context in which the event occurred						X
eventName		semBCreate (10008)		The name of the event associated with this icon						X
semValue		semValue : 0x3a3964		The ID of the task that owns the semaphore or NULL						X
semOptions		options : SEM_Q_FIFO		Semaphore queueing option: SEM_Q_PRIORITY or SEM_Q_FIFO						X
semId		semId : 0x3fd900		ID of the created binary semaphore						X

Application code called the semCCreate( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.033973		The time at which the event occurred						X
context		Context : tLogTask (0x3a3964)		The context in which the event occurred						X
eventName		semCCreate (10009)		The name of the event associated with this icon						X
semValue		semValue : 0		Initial count of the semaphore						X
semOptions		options : SEM_Q_FIFO		Semaphore queueing option: SEM_Q_PRIORITY or SEM_Q_FIFO						X
semId		semId : 0x3a0fa4		ID of the created counting semaphore						X

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):

• The FTP server daemon task.

• The TFTP server task.

In addition, system code creates and uses these mutex semaphores:

• The volume-locking semaphore in the dosFs file system.

• The volume-locking semaphore, the fd-access semaphore, and each fd's semaphore in the raw file system.

• The volume-locking semaphore in the RT-11 file system.

• The object module management semaphores.

• The network mutual exclusion semaphore.

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.033731		The time at which the event occurred				X		X
context		Context : tLogTask (0x3a3964)		The context in which the event occurred				X		X
eventName		semDelete (10010)		The name of the event associated with this icon				X		X
semId		semId : 0x3a0fa4		ID of the semaphore to delete				X		X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.033633		The time at which the event occurred						X
context		Context : tLogTask (0x3a3964)		The context in which the event occurred						X
eventName		semFlush (10011)		The name of the event associated with this icon						X
semId		semId : 0x3a0f54		ID of the semaphore to flush						X

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):

• The FTP server daemon task.

• The TFTP server task.

In addition, system code creates and uses these mutex semaphores:

• The volume-locking semaphore in the dosFs file system.

• The volume-locking semaphore, the fd-access semaphore, and each fd's semaphore in the raw file system.

• The volume-locking semaphore in the RT-11 file system.

• The object module management semaphores.

• The network mutual exclusion mechanism.

• The memory management mechanism.

• The serial devices management mechanism (tyLib).

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).

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.014918		The time at which the event occurred				X		X
context		Context : t2 (0x3dd918)		The context in which the event occurred				X		X
eventName		semGive (10012)		The name of the event associated with this icon				X		X
recurse		recurse : 0		For mutual exclusion semaphores, the number of gives that must occur before this semaphore is released						X
semValue		semValue : 0x33dd918		The value before the semGive, as follows: For a binary semaphore, the ID of the current task or NULL For a counting semaphore, the current count For a mutex semaphore, the ID of the task that owns this semaphore or NULL						X
semId		semId : 0x3a0f54		ID of the semaphore to give				X		X

System or application code called the semMCreate( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time: 0.033929		The time at which the event occurred						X
context		Context : tLogTask (0x3a3964)		The context in which the event occurred						X
eventName		semMCreate (10013)		The name of the event associated with this icon						X
semValue		semValue : 0		ID of task that owns the mutual exclusion semaphore (the semaphore is not owned at creation, so it is always NULL)						X
semOptions		semOptions : SEM_Q_FIFO		Semaphore option(s); see the VxWorks Programmer's Guide for valid combinations: SEM_Q_PRIORITY, SEM_Q_FIFO, SEM_DELETE_SAFE, SEM_INVERSION_SAFE						X
semId		semId : 0x3a00a4		ID of the created mutual exclusion semaphore						X

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).

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.011881		The time at which the event occurred						X
context		Context : t4 (0x3a6588)		The context in which the event occurred						X
eventName		semMGiveForce (10014)		The name of the event associated with this icon						X
semValue		semValue : 0		The ID of the task that owns the semaphore or NULL						X
semOptions		semOptions : SEM_Q_PRIORITY		Semaphore option: SEM_Q_PRIORITY, SEM_Q_FIFO, SEM_DELETE_SAFE, or SEM_INVERSION_SAFE						X
semId		semId : 0x5dafc		ID of the mutual exclusion semaphore to give without restrictions						X

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):

• The FTP server daemon task.

• The TFTP server task.

In addition, system code creates and uses these mutex semaphores:

• The volume-locking semaphore in the dosFs file system.

• The volume-locking semaphore, the fd-access semaphore, and each fd's semaphore in the raw file system.

• The volume-locking semaphore in the RT-11 file system.

• The object module management semaphores.

• The network mutual exclusion mechanism.

• The memory management mechanism.

• The serial devices management mechanism (tyLib).

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.042625		The time at which the event occurred				X		X
context		Context : t4 (0x3a6588)		The context in which the event occurred				X		X
eventName		semTake (10015)		The name of the event associated with this icon				X		X
recurse		recurse : 0		For mutual exclusion semaphores, the number of gives that must occur before this semaphore is released						X
semValue		semValue : 0		The value before the semTake, as follows: For a binary semaphore, the ID of the current task or NULL. For a counting semaphore, the current count. For a mutex semaphore, the ID of the task that owns this semaphore or NULL.						X
semId		semId : 0x3a0804		ID of the semaphore to take				X		X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.1530		The time at which the event occurred				X		X
context		Context : t2 (0x3dd918)		The context in which the event occurred				X		X
eventName		kill (10027)		The name of the event associated with this icon				X		X
taskId		taskId : 0xf90f6c		ID of the task to receive the signal				X		X
signo		signo : 0x1e		Signal number						X

Application code called the pause( ) routine.

The currently executing task makes a transition to the suspended state, and a context switch occurs.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.011881		The time at which the event occurred				X		X
context		Context : tLogTask (0xfa0dc0)		The context in which the event occurred				X		X
eventName		pause (10026)		The name of the event associated with this icon				X		X
taskId		taskId : 0x39d830		ID of the current task				X		X

Application code called the signal( ), sigaction( ), or sigvec( ) routine.

None.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 1.1467		The time at which the event occurred						X
context		Context : task5 (0x39ecb4)		The context in which the event occurred						X
eventName		signal ( 10024)		The name of the event associated with this icon						X
handler		handler : 0x3fdb20		Pointer to the function to handle the signal, or SIG_DFL or SIG_IGN						X
signo		signo : 0x5		Signal number						X

Application code called the sigsuspend( ) routine.

The currently executing task makes a transition to the suspended state, and a context switch occurs.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.011881		The time at which the event occurred				X		X
context		Context : t2 (0x3dd918)		The context in which the event occurred				X		X
eventName		sigsuspend ( 10025)		The name of the event associated with this icon				X		X
sigset		sigset : 0x40000000		The sigset_t structure that holds the signal set mask				X		X

The signalled task is interrupted and the signal handler runs in that task's context.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.00195		The time at which the event occurred						X
context		Context : t4 (0xf90f6c)		The context in which the event occurred						X
eventName		sigwrapper (10029)		The name of the event associated with this icon						X
signo		signo : 0xf90f6c		Signal number						X
taskId		taskId : 0x3dd918		ID of the task that was signalled						X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.6565		The time at which the event occurred						X
context		Context : taskTest (0xf9664c)		The context in which the event occurred						X
eventName		safePend (10028)		The name of the event associated with this icon						X
taskId		taskId : 0xf9b5fc		ID of the task to pend or unpend						X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 3.99884		The time at which the event occurred				X		X
context		Context : t14 (0x38bd08)		The context in which the event occurred				X		X
eventName		taskDelay (10002)		The name of the event associated with this icon				X		X
delayTicks		delay : 60		Number of ticks to delay task				X		X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.09537		The time at which the event occurred				X		X
context		Context : tLogTask (0x3a468c)		The context in which the event occurred				X		X
eventName		taskDelete (10001)		The name of the event associated with this icon				X		X
safeCnt		safeCnt : 1		Number of taskSafe( ) routines issued for this task						X
taskId		taskId : 0x38bd08		ID of the task to delete				X		X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.024345		The time at which the event occurred				X		X
context		Context : tLogTask (0x39bf18)		The context in which the event occurred				X		X
eventName		taskPrioritySet (10003)		The name of the event associated with this icon				X		X
oldPriority		priority : 100		Old priority of affected task				X		X
newPriority		priority : 120		New priority of affected task				X		X
taskId		taskId : 0x38bca4		ID of affected task				X		X

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.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.014816		The time at which the event occurred				X		X
context		Context : tLogTask (0x39bf18)		The context in which the event occurred				X		X
eventName		taskResume (10005)		The name of the event associated with this icon				X		X
priority		priority : 120		Task priority, 0 -- 255						X
taskId		taskId : 0x381d44		ID of the task to resume				X		X

Application code called the taskSafe( ) routine.

No immediate effect. However, see safePend.

Information Collected.

  

Event Parameter		Sample Data		Description		C S E		T S T		A I L
timeStamp		Time : 0.298828		The time at which the event occurred						X
context		Context : tLogTask (0x3a468c)		The context in which the event occurred						X
eventName		taskSafe (10006)		The name of the event associated with this icon						X
safeCnt		safeCnt : 1		Number of calls to taskSafe( ) before this one, plus the number of times this task has taken a deletion-safe mutex semaphore						X
taskId		taskId : 0x3a468c		ID of the task to make safe						X