From 41a02591b9d199a82bb24c23f3828102375137de Mon Sep 17 00:00:00 2001 From: Robin Haberkorn Date: Mon, 3 Jul 2023 04:27:49 +0300 Subject: introduced TECO_DEBUG_CLEANUP to mark destructors that should only be used for debug builds * There is cleanup that is not strictly necessary, because it only frees memory which is freed on program termination anyway. * However, it helps to explicitly free everything for debugging memory leaks via Valgrind. * The new macro reduces the number of #ifdef statements. * On NDEBUG, the code of these functions will still be eliminated. * If functions are referenced only from the destructor, there will be no unused function warnings, even in NDEBUG. --- src/memory.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'src/memory.c') diff --git a/src/memory.c b/src/memory.c index 6d7645c..d26b794 100644 --- a/src/memory.c +++ b/src/memory.c @@ -628,8 +628,7 @@ teco_memory_stop_limiting(void) g_mutex_unlock(&teco_memory_mutex); } -#ifndef NDEBUG -static void __attribute__((destructor)) +static void TECO_DEBUG_CLEANUP teco_memory_cleanup(void) { if (!teco_memory_thread) @@ -642,7 +641,6 @@ teco_memory_cleanup(void) g_thread_join(teco_memory_thread); } -#endif #else /* !NEED_POLL_THREAD */ -- cgit v1.2.3