From 3015b86bab07d7892add3d74cfc69320015c6614 Mon Sep 17 00:00:00 2001 From: "Fred T. Hamster" Date: Tue, 10 Feb 2026 21:53:37 -0500 Subject: [PATCH] turning on the callstack tracker for dev living dangerously. want to see if any problems actually exist from this code. next step would be turning off the callstack tracker and back on the memory checker, which is a broken kludge festival if i remember properly. --- production/feisty_meow_config.ini | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/production/feisty_meow_config.ini b/production/feisty_meow_config.ini index 959cc908..d5e8494a 100644 --- a/production/feisty_meow_config.ini +++ b/production/feisty_meow_config.ini @@ -84,6 +84,6 @@ endif # methods with a way to know how they were invoked. to get this information. # the invoker must be fitted with FUNCDEF macros. ifeq "$(BOOT_STRAPPING)" "" -# DEFINITIONS += ENABLE_CALLSTACK_TRACKING + DEFINITIONS += ENABLE_CALLSTACK_TRACKING endif -- 2.34.1