From 42eb9ee55fd306fb14aad149420787a9aafe3d83 Mon Sep 17 00:00:00 2001 From: Quincey Koziol Date: Thu, 13 Nov 2003 13:15:42 -0500 Subject: [svn-r7846] Purpose: Bug fix. Description: The new routines added for H5MM_[m|c]alloc were causing the function stack code to infinitely recurse while allocating room for the thread-specific information (when thread-safety was turned on). Solution: Call HDmalloc directly instead of H5MM_malloc Platforms tested: FreeBSD 4.9 (sleipnir) Changed are not tested in h5committest --- src/H5FS.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/H5FS.c b/src/H5FS.c index 9ec80de..0c02034 100644 --- a/src/H5FS.c +++ b/src/H5FS.c @@ -27,7 +27,6 @@ */ #include "H5private.h" /* Generic Functions */ #include "H5FSprivate.h" /* Private function stack routines */ -#include "H5MMprivate.h" /* Memory management functions */ #ifdef H5_HAVE_FUNCSTACK @@ -86,7 +85,7 @@ H5FS_get_stack(void) fstack = pthread_getspecific(H5TS_funcstk_key_g); if (!fstack) { /* no associated value with current thread - create one */ - fstack = (H5FS_t *)H5MM_malloc(sizeof(H5FS_t)); + fstack = (H5FS_t *)HDmalloc(sizeof(H5FS_t)); /* Don't use H5MM_malloc() here, it causes infinite recursion */ pthread_setspecific(H5TS_funcstk_key_g, (void *)fstack); } -- cgit v0.12