*@deprecated This method is inherently unsafe. Stopping a thread with
* Thread.stop causes it to unlock all of the monitors that it
* has locked (as a natural consequence of the unchecked
*<code>ThreadDeath</code> exception propagating up the stack). If
* any of the objects previously protected by these monitors were in
* an inconsistent state, the damaged objects become visible to
* other threads, potentially resulting in arbitrary behavior. Many
* uses of <code>stop</code> should be replaced by code that simply
* modifies some variable to indicate that the target thread should
* stop running. The target thread should check this variable
* regularly, and return from its run method in an orderly fashion
*if the variable indicates that it is to stop running. If the
* target thread waits forlong periods (on a condition variable,*for example), the <code>interrupt</code> method should be used to
* interrupt the wait.* For more information, see
*<a href="{@docRoot}/../technotes/guides/concurrency/threadPrimitiveDeprecation.html">Why
* are Thread.stop, Thread.suspend and Thread.resume Deprecated?</a>.
场景Thread.stop()为何废弃被放弃的原因解释stop方法抛除ThreadDeath,这个异常会在栈传播,导致所有监视器被释放,这导致不可以预料的后果 * @deprecated This method is inherently unsafe. Stopping a thread with * Thread.stop causes it to unlock all of the monitors that it * has lo