fix(sync): fix the debug printing of Mutex and RecursiveMutex when CPU Lock is active

Author: yvt

CHANGELOG.md

@@ -14,6 +14,10 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
 - Upgrade `tokenlock` to `0.3.4`
 - Using the new version of `tokenlock`, some atomics-based hacks were removed. This might marginally improve the runtime performance as the compiler is given more leeway to optimize memory accesses.
 
+### Fixed
+
+- The debug printing of `Mutex` and `RecursiveMutex` in an invalid context now produces a message that makes sense.
+
 ## [0.1.1] - 2020-12-20
 
 ### Added

src/r3/src/sync/mutex.rs

@@ -242,7 +242,7 @@ impl<System: Kernel, T: fmt::Debug + 'static> fmt::Debug for Mutex<System, T> {
                 struct BadContextPlaceholder;
                 impl fmt::Debug for BadContextPlaceholder {
                     fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
-                        f.write_str("<CPU context active>")
+                        f.write_str("<bad context>")
                     }
                 }
 

src/r3/src/sync/recursive_mutex.rs

@@ -335,7 +335,7 @@ impl<System: Kernel, T: fmt::Debug + 'static> fmt::Debug for RecursiveMutex<Syst
                 struct BadContextPlaceholder;
                 impl fmt::Debug for BadContextPlaceholder {
                     fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
-                        f.write_str("<CPU context active>")
+                        f.write_str("<bad context>")
                     }
                 }