W
William Stacey
..Net's Mutex object seems to ignore (or internally consume) a WAIT_ABANDONED
condition if the owning thread is aborted. The next thread waiting on the
Mutex gets the mutex with no error. If this is by design, it would seem to
be a dangerous design choice. Normally another thread would want to know
this information as the thing the mutex was protecting could (and probably
is) be in an inconsistant state, yet the 2nd thread will march on like
nothing was wrong. Am I missing something?
condition if the owning thread is aborted. The next thread waiting on the
Mutex gets the mutex with no error. If this is by design, it would seem to
be a dangerous design choice. Normally another thread would want to know
this information as the thing the mutex was protecting could (and probably
is) be in an inconsistant state, yet the 2nd thread will march on like
nothing was wrong. Am I missing something?