From 4d829e3d292cc7ac6c2c5980591b88c59abf0621 Mon Sep 17 00:00:00 2001 From: Glenn Maynard Date: Wed, 8 Sep 2004 21:17:43 +0000 Subject: [PATCH] wait, no. It's GetThreadBacktraceContext's job to suspend the thread. --- stepmania/src/archutils/Unix/CrashHandler.cpp | 7 ------- 1 file changed, 7 deletions(-) diff --git a/stepmania/src/archutils/Unix/CrashHandler.cpp b/stepmania/src/archutils/Unix/CrashHandler.cpp index 3589387bbe..9817cdeefe 100644 --- a/stepmania/src/archutils/Unix/CrashHandler.cpp +++ b/stepmania/src/archutils/Unix/CrashHandler.cpp @@ -364,13 +364,6 @@ void ForceCrashHandler( const char *reason ) void ForceCrashHandlerDeadlock( CString reason, uint64_t iID ) { - /* How can this possibly work without suspending the thread first? What - * stops the thread from returning from the function it was in when - * GetThreadBacktraceContext was called and then changing the stack? - */ - /* There's just no good way to pause other threads, that doesn't result in us - * being paused, weird stuff happening to the TTY, or kernel hung processes. - * We just hope that we backtrace in time (which we almost always do). */ #if defined(DARWIN) SuspendThread(iID); #endif