The death of a thread (and any subsequent notifications etc.) Is effectively just an indication that the thread will never execute any more code; it does not guarantee that the operating system has yet finished removing the thread.
Death is just a simple thread of instructions, that thread will not execute any code. But this does not guarantee that the operating system has been out of the thread.
When a thread terminates, the operating system cleans up all resources still allocated to the thread; this includes closing any sessions which it had open. Closing a session involves notifying the other party in the session that the thread has disconnected so that it can do its own cleanup; the operating system needs to keep the dead t0hread''s data structures until all of this disconnection activity has finished.
When the thread terminates, the operating system will clean up all the resources allocated to the thread, which also includes close any thread is already open session. Closed session to inform the rest of the session, told them that the thread has not connected to the session, so that they can perform their own clean-up. Death of the operating system must be maintained all the data structures thread until the broken end of the process.
If a thread terminates, there may be a period of time during which any attempt to create a new thread of the same name fails with KErrAlreadyExists.
If the thread is terminated, then the need for a cycle, in this cycle, any thread can not create the same name, and the failure to KErrAlreadyExists exit.
Recommended links:
Quad Band Swivel Screen Cellphone With
3GPP to WMV
MPG to DivX
MPEG4 to MPEG
No comments:
Post a Comment