bd5bc49d05
This test required a newer version of cdb than was previously enabled in CI thus leading to some bitrot in the test since the time it was originally created. With the update to the `windows-latest` image last week, we're now running this test in CI and thus uncovered the regression. I've updated the test and it now passes.
38 lines
1.2 KiB
Rust
38 lines
1.2 KiB
Rust
// Testing the display of Mutex and MutexGuard in cdb.
|
|
|
|
// cdb-only
|
|
// min-cdb-version: 10.0.21287.1005
|
|
// compile-flags:-g
|
|
|
|
// === CDB TESTS ==================================================================================
|
|
//
|
|
// cdb-command:g
|
|
//
|
|
// cdb-command:dx m,d
|
|
// cdb-check:m,d [Type: std::sync::mutex::Mutex<i32>]
|
|
// cdb-check: [...] inner [Type: std::sys_common::mutex::MovableMutex]
|
|
// cdb-check: [...] poison [Type: std::sync::poison::Flag]
|
|
// cdb-check: [...] data : 0 [Type: core::cell::UnsafeCell<i32>]
|
|
|
|
//
|
|
// cdb-command:dx m.data,d
|
|
// cdb-check:m.data,d : 0 [Type: core::cell::UnsafeCell<i32>]
|
|
// cdb-check: [<Raw View>] [Type: core::cell::UnsafeCell<i32>]
|
|
|
|
//
|
|
// cdb-command:dx lock,d
|
|
// cdb-check:lock,d : Ok [Type: enum$<core::result::Result<std::sync::mutex::MutexGuard<i32>,enum$<std::sync::poison::TryLockError<std::sync::mutex::MutexGuard<i32> >, 0, 1, Poisoned> > >]
|
|
// cdb-check: [variant] : Ok
|
|
// cdb-check: [...] __0 [Type: std::sync::mutex::MutexGuard<i32>]
|
|
|
|
use std::sync::Mutex;
|
|
|
|
#[allow(unused_variables)]
|
|
fn main()
|
|
{
|
|
let m = Mutex::new(0);
|
|
let lock = m.try_lock();
|
|
zzz(); // #break
|
|
}
|
|
|
|
fn zzz() {}
|