Windows XP does not explicitly detect deadlock situations for threads using dispatcher objects. How might threads using dispatcher objects create a deadlock?What mechanisms does Windows XP include to help avoid these situations?
What will be an ideal response?
Consider a situation where two threads each hold a resource. If each thread waits for
control of the other’s resource without relinquishing its own resource, a deadlock can occur.
Windows XP allows threads to specify a maximum wait time for a dispatcher object to avoid
this situation.Also, a thread can reacquire a mutex or a semaphore that it already owns.
You might also like to view...
By default, the classpath consists only of the ________. However, the classpath can be modified by providing the ________ option to the javac compiler.
a. root directory of the package, -d. b. current directory, -d. c. root directory of the package, -classpath. d. current directory, -classpath.
Console.Write("anExample".IndexOf("a")); returns ____.
A. null B. 4 C. 04 D. 0