fix(ndk): remove possibility the the bsg_global_env->handling_crash…

… or `unwinding_crash_stack` CAS succeed spuriously
bugsnag · Jan 8, 2024 · 6fb06dc · 6fb06dc
1 parent ba43ff7
commit 6fb06dc
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/bugsnag-plugin-android-ndk/src/main/jni/bugsnag_ndk.c b/bugsnag-plugin-android-ndk/src/main/jni/bugsnag_ndk.c
@@ -68,7 +68,7 @@ bool bsg_run_on_error() {
 }
 
 bool bsg_begin_handling_crash() {
-  static bool expected = false;
+  bool expected = false;
   return atomic_compare_exchange_strong(&bsg_global_env->handling_crash,
                                         &expected, true);
 }

diff --git a/bugsnag-plugin-android-ndk/src/main/jni/utils/stack_unwinder.cpp b/bugsnag-plugin-android-ndk/src/main/jni/utils/stack_unwinder.cpp
@@ -142,7 +142,7 @@ ssize_t bsg_unwind_crash_stack(bugsnag_stackframe stack[BUGSNAG_FRAMES_MAX],
   // we always check unwinding_crash_stack and set *before* attempting to
   // retrieve the crash unwinder to avoid picking up an unwinder that is about
   // to be destroyed by bsg_unwinder_refresh
-  static bool expected = false;
+  bool expected = false;
   if (!std::atomic_compare_exchange_strong(&unwinding_crash_stack, &expected,
                                            true)) {
     return 0;