Want this question answered?
No, a thread can't create aprocess, because the environment of the thread is a part of a process which created this thread.
When a thread is created the threads does not require any new resources to execute the thread shares the resources like memory of the process to which they belong to. The benefit of code sharing is that it allows an application to have several different threads of activity all within the same address space. Whereas if a new process creation is very heavyweight because it always requires new address space to be created and even if they share the memory then the inter process communication is expensive when compared to the communication between the threads
No. A thread is a part of a process, but a process can not be part of a thread. Processes are always "at the top."
The same metaphor: the difference of a person (thread) and a family (process) A process has at least 1 thread and may have many threads, while 1 thread must live within a process
Execution context within a process is called Thread. Threads run, process does not. Every process starts with one thread.
There r some resources shared by different threads o the same process while some r not. The threads shares the address space,file,global variables. But each threads has its own stack , copy of registers(including PC).
Light weight is called as a thread which runs inside a process and a heavy weight is a system process. As the thread share the memory of heavy weight then we can say that it is not taking any additional resources(memory) to execute. As a process is a combination of one of more then one threads and each process is having the separate memory location so it is very easy for thread to communicate with each other as compare to two process communicate because thread communicate within same memory but process communicate with other process having different memory location. Here we can consider light weight as a thread and heavy weight as a process.
By a Thread was created in 2009-01.
yes, because if process is terminated then its related thread has no work. After completion of process the kernel generates a thread that will cancelled the thread in order to save the time and memory of CPU.
A thread is basically a lightweight process.
The child process is initially running its parent' s program, with its parent' s virtual memory, file descriptors, and so on copied.The child process can modify its memory, close file descriptors, and the like without affecting its parent, and vice versa. When a program creates another thread, though, nothing is copied.The creating and the created thread share the same memory space, file descriptors, and other system resources as the original. If one thread changes the value of a variable, for instance, the other thread subsequently will see the modified value. Similarly, if one thread closes a file descriptor, other threads may not read from or write to that file descriptor.
what process turn the yarn into thread