T-Kernel Specification (1.B0.02)

36 CHAPTER 4. T-KERNEL/OS FUNCTIONS
[Additional Notes]
When a task is terminated by tk ter tsk, the resources acquired by the task up to that time (memory
blocks, semaphores, etc.) are not automatically freed. The user is responsible for releasing such resources
before the task terminates.
As a rule, the task priority and other information included in the TCB are reset when the task returns
to DORMANT state. If, for example, the task priority is changed by tk chg pri and later terminated
by tk ter tsk, the task priority reverts to the startup priority (itskpri) designated when the task was
started. It does not keep the task priority in effect at the time tk ter tsk was executed.
Forcible termination of another task is intended for use only by a debugger or a few other tasks closely
related to the OS. As a rule, this system call is not to be used by ordinary applications or middleware,
for the following reason.
Forced termination occurs regardless of the running state of the target task.
If, for example, a task were forcibly terminated while the task was calling a middleware function, the
task would terminate right while the middleware was executing. If such a situation were allowed, normal
operation of the middleware could not be guaranteed.
This is an example of how task termination cannot be allowed when the task status (what it is executing)
is unknown. Ordinary applications therefore must not use the forcible termination function.
Copyright c○ 2002, 2003 by T-Engine Forum
T-Kernel 1.B0.02