From 0c00335627e4ec5a1f6dea041d5ad2d046fb5fa5 Mon Sep 17 00:00:00 2001 From: Vinnie Falco Date: Mon, 5 Aug 2013 09:19:34 -0700 Subject: [PATCH] Fatal error in ~Thread if thread still running (undefined behavior) --- modules/beast_core/threads/beast_Thread.cpp | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/modules/beast_core/threads/beast_Thread.cpp b/modules/beast_core/threads/beast_Thread.cpp index b2c018489..eb6167740 100644 --- a/modules/beast_core/threads/beast_Thread.cpp +++ b/modules/beast_core/threads/beast_Thread.cpp @@ -40,10 +40,7 @@ Thread::~Thread() To avoid this type of nastiness, always make sure you call stopThread() before or during your subclass's destructor. */ - bassert (! isThreadRunning()); - - if (isThreadRunning()) - FatalError ("Thread is still running", __FILE__, __LINE__); + fatal_require (! isThreadRunning()); } //==============================================================================