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/spawn.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'src/spawn.c') diff --git a/src/spawn.c b/src/spawn.c index a30e6b2..7515fd6 100644 --- a/src/spawn.c +++ b/src/spawn.c @@ -789,8 +789,7 @@ teco_spawn_idle_cb(gpointer user_data) return G_SOURCE_CONTINUE; } -#ifndef NDEBUG -static void __attribute__((destructor)) +static void TECO_DEBUG_CLEANUP teco_spawn_cleanup(void) { g_source_unref(teco_spawn_ctx.idle_src); @@ -801,4 +800,3 @@ teco_spawn_cleanup(void) if (teco_spawn_ctx.error) g_error_free(teco_spawn_ctx.error); } -#endif -- cgit v1.2.3