From 9f57b53569e732eb9c1da81b287decbce1cb98f1 Mon Sep 17 00:00:00 2001 From: russell Date: Tue, 9 Dec 2008 22:34:55 +0000 Subject: Merged revisions 162414 via svnmerge from https://origsvn.digium.com/svn/asterisk/trunk ................ r162414 | russell | 2008-12-09 16:25:06 -0600 (Tue, 09 Dec 2008) | 16 lines Merged revisions 162413 via svnmerge from https://origsvn.digium.com/svn/asterisk/branches/1.4 ........ r162413 | russell | 2008-12-09 16:17:39 -0600 (Tue, 09 Dec 2008) | 8 lines Remove the test_for_thread_safety() function completely. The test is not valid. Besides, if we actually suspected that recursive mutexes were not working, we would get a ton of LOG_ERROR messages when DEBUG_THREADS is turned on. (inspired by a discussion on the asterisk-dev list) ........ ................ git-svn-id: http://svn.digium.com/svn/asterisk/branches/1.6.1@162416 f38db490-d61c-443f-a65b-d21fe96a405b --- main/asterisk.c | 4 ---- 1 file changed, 4 deletions(-) (limited to 'main/asterisk.c') diff --git a/main/asterisk.c b/main/asterisk.c index c7c4ec823..e85479b15 100644 --- a/main/asterisk.c +++ b/main/asterisk.c @@ -3290,10 +3290,6 @@ int main(int argc, char *argv[]) } #endif - /* Test recursive mutex locking. */ - if (test_for_thread_safety()) - ast_verbose("Warning! Asterisk is not thread safe.\n"); - ast_event_init(); ast_makesocket(); -- cgit v1.2.3