采用锁的程序必须非常小心，以免产生死锁的情况。
A program taking a lock must take great care not to create a deadlock situation.
这个版本的程序演示了一个产生死锁的一般来源：程序员的错误。
This version of the program demonstrates a common source of deadlocks: programmer stupidity.
您可将注意力放到应用逻辑中，而不必担心会产生死锁而导致系统突然宕机。
You can put your concentration back on your application logic and not worry so much about creating a deadlock that will bring your system to a sudden halt.
如果线程在不首先解除互斥锁的情况下尝试重新锁定该互斥锁，则会产生死锁。
A thread attempting to re lock this mutex without first unlocking it shall deadlock.
如果两个用户进程分别锁定了不同的资源，接着又试图锁定对方所锁定的资源，就会产生死锁。
If two users process parts, the lock decided different resource, try to lock up place of calm the other side to lock up decided resource again then, can produce dead lock.
它证明了该CLI规范还同时保证了运行库不允许类型构造函数产生死锁的情形，除非用户代码显式采用了附加锁。
It turns out the CLI specification also guarantees that the runtime will not allow type constructors to create a deadlock situation, unless additional locks are explicitly taken by user code.
它证明了该CLI规范还同时保证了运行库不允许类型构造函数产生死锁的情形，除非用户代码显式采用了附加锁。
It turns out the CLI specification also guarantees that the runtime will not allow type constructors to create a deadlock situation, unless additional locks are explicitly taken by user code.
应用推荐