From ab46f6b988c9c6f1e4fdc0d8f549dd64a1c07fcf Mon Sep 17 00:00:00 2001 From: Matt Corallo Date: Tue, 10 Jan 2023 06:37:39 +0000 Subject: [PATCH] Make `debug_sync` regex more robust On windows the symbol names appear to sometimes be truncated, which causes the symbol name to not include the `::new` at the end. This causes the regex to mis-match and track the wrong location for the mutex construction, leading to bogus lockorder violations. For example, in testing the following symbol name appeared on Windows, without the function name itself: `lightning::debug_sync::RwLock,std::collections::hash::map::RandomState> >::` --- lightning/src/sync/debug_sync.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lightning/src/sync/debug_sync.rs b/lightning/src/sync/debug_sync.rs index ac82475f9..9f7caa2c1 100644 --- a/lightning/src/sync/debug_sync.rs +++ b/lightning/src/sync/debug_sync.rs @@ -77,7 +77,7 @@ fn get_construction_location(backtrace: &Backtrace) -> String { // Find the first frame that is after `debug_sync` (or that is in our tests) and use // that as the mutex construction site. Note that the first few frames may be in // the `backtrace` crate, so we have to ignore those. - let sync_mutex_constr_regex = regex::Regex::new(r"lightning.*debug_sync.*new").unwrap(); + let sync_mutex_constr_regex = regex::Regex::new(r"lightning.*debug_sync").unwrap(); let mut found_debug_sync = false; for frame in backtrace.frames() { for symbol in frame.symbols() { -- 2.39.5