-
Notifications
You must be signed in to change notification settings - Fork 31
crashpad::`anonymous namespace'::HandleAbortSignal #1038
Copy link
Copy link
Open
Labels
Description
Sentry Issue: BINARYNINJA-2K
STATUS_FATAL_APP_EXIT / 0x7ff6e3e558c6: Fatal Error: STATUS_FATAL_APP_EXIT / 0x7ff6e3e558c6
File "crashpad_client_win.cc", line 230, in crashpad::`anonymous namespace'::HandleAbortSignal
File "throw.cpp", line 79, in _CxxThrowException
File "thread0.cpp", line 33, in std::_Throw_Cpp_error
File "thread", line 127, in std::thread::join
File "debuggercontroller.cpp", line 50, in BinaryNinjaDebugger::DebuggerController::~DebuggerController
...
(22 additional frame(s) were not displayed)
@bdash says:
The immediate cause of the crash is that
DebuggerController's destructor callsstd::thread::joinonm_debuggerEventThreadwhile it is executing on the debugger event thread. Attempting to join the current thread results instd::system_error(std::errc::resource_deadlock_would_occur)being thrown, and since that exception is not handled the app exits.
DebuggerControlleris destroyed on this thread because theDebuggerFileAccessoris the final reference to the controller, and it is deleted in response toTargetExitedEventType,DetachedEventType, andLaunchFailureEventType
Reactions are currently unavailable