diff options
author | Edward Betts <edward@4angle.com> | 2017-02-21 14:03:07 +0300 |
---|---|---|
committer | Alexander Köplinger <alex.koeplinger@outlook.com> | 2017-02-21 14:03:07 +0300 |
commit | 539a6580da4236c0bd9efae80acb49dd38d408a6 (patch) | |
tree | b7292de0ce60b9bdbedbdb8166d8718d96bcc86e /data | |
parent | 4ccd94d7ccf69cc52532ea920b2d1b48f9c6a7cc (diff) |
correct spelling mistakes (#4405)
Diffstat (limited to 'data')
-rw-r--r-- | data/lock-decoder/LockTracerDecoder.cs | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/data/lock-decoder/LockTracerDecoder.cs b/data/lock-decoder/LockTracerDecoder.cs index 08576f1a7de..1471ea51181 100644 --- a/data/lock-decoder/LockTracerDecoder.cs +++ b/data/lock-decoder/LockTracerDecoder.cs @@ -86,7 +86,7 @@ LOCK RULES Simple locks: Can be acquired at any point regardless of which locks are taken or not. No other locks can be acquired or released while holding a simple lock. - Reentrancy is not recomended. (warning) + Reentrancy is not recommended. (warning) Simple locks are leaf locks on the lock lattice. Complex locks: @@ -129,7 +129,7 @@ ERROR: tried to acquire lock DomainLock at mono_domain_code_reserve_align while WARNING: tried to acquire lock ImageDataLock at mono_image_init_name_cache while holding ImageDataLock at mono_class_from_name WARNING: tried to acquire lock ImageDataLock at mono_image_init_name_cache while holding ImageDataLock at mono_image_add_to_name_cache Both of those happen when filling up the name_cache, as it needs to alloc image memory. - This one is fixable by spliting mono_image_init_name_cache into a locked and an unlocked variants and calling them appropriatedly. + This one is fixable by splitting mono_image_init_name_cache into a locked and an unlocked variants and calling them appropriately. */ |