From 62f2dd7c6c89ca44f2096f535962b63f26f57730 Mon Sep 17 00:00:00 2001 From: Mason Reed Date: Sat, 19 Oct 2024 20:53:10 -0400 Subject: Remove ability to panic on pre-initialized logger in rust Typically this would never occur, however due to the mystical nature of linkers this somehow has happened outside of demo builds --- rust/examples/workflow/src/lib.rs | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'rust/examples/workflow/src') diff --git a/rust/examples/workflow/src/lib.rs b/rust/examples/workflow/src/lib.rs index 3e295c51..47a8d2c8 100644 --- a/rust/examples/workflow/src/lib.rs +++ b/rust/examples/workflow/src/lib.rs @@ -5,7 +5,6 @@ use binaryninja::workflow::{Activity, AnalysisContext, Workflow}; use log::LevelFilter; const RUST_ACTIVITY_NAME: &'static str = "analysis.plugins.rustexample"; -// TODO: runOnce needs to be on... const RUST_ACTIVITY_CONFIG: &'static str = r#"{ "name": "analysis.plugins.rustexample", "title" : "Rust Example", @@ -56,7 +55,7 @@ fn example_activity(analysis_context: &AnalysisContext) { #[no_mangle] #[allow(non_snake_case)] pub extern "C" fn CorePluginInit() -> bool { - binaryninja::logger::init(LevelFilter::Debug).unwrap(); + binaryninja::logger::init(LevelFilter::Info); log::info!("Initialized the plugin"); -- cgit v1.3.1