From d542e14120bfd2a7a6a705a7a70c6bfedf53a5c7 Mon Sep 17 00:00:00 2001 From: Brian Barrett Date: Thu, 10 Nov 2005 04:13:56 +0000 Subject: [PATCH] * for some reason, some versions of linux didn't like that call to mmap. The test isn't really needed to make sure the malloc intercept code was working, so just revert to not checking for now. This should go to the 1.0 branch, as what is there now is causing issues. This commit was SVN r8081. --- opal/memory/memory.c | 14 -------------- 1 file changed, 14 deletions(-) diff --git a/opal/memory/memory.c b/opal/memory/memory.c index c2fb293795..4bdd715b36 100644 --- a/opal/memory/memory.c +++ b/opal/memory/memory.c @@ -52,7 +52,6 @@ static int have_been_called = 0; int opal_mem_free_init(void) { - void *tmp; OBJ_CONSTRUCT(&callback_list, opal_list_t); opal_atomic_init(&callback_lock, OPAL_ATOMIC_UNLOCKED); @@ -61,19 +60,6 @@ opal_mem_free_init(void) run_callbacks = false; opal_atomic_mb(); - /* make sure things actually work - map then unmap a page */ - tmp = mmap(0, 1, PROT_READ|PROT_WRITE, MAP_ANON, -1, 0); - munmap(tmp, 1); - if (0 == have_been_called) { - if (have_free_support) { - opal_output(0, "WARNING: free() and munmap() hooks inoperative" - "disabling memory hooks. This"); - opal_output(0, "WARNING: may cause performance degredation."); - } - - have_free_support = false; - } - return OMPI_SUCCESS; }