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/error.c | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'src/error.c') diff --git a/src/error.c b/src/error.c index 7c4e151..45428df 100644 --- a/src/error.c +++ b/src/error.c @@ -161,10 +161,7 @@ teco_error_add_frame_toplevel(void) teco_error_add_frame(TECO_FRAME_TOPLEVEL, 0); } -#ifndef NDEBUG -__attribute__((destructor)) -#endif -void +void TECO_DEBUG_CLEANUP teco_error_clear_frames(void) { teco_stailq_entry_t *entry; -- cgit v1.2.3