When working on nolibc, debug information is very valuable.
I find myself adding this flag in many patchsets.

Enable debug information unconditionally, as there is no downside to it.

Signed-off-by: Thomas Weißschuh <[email protected]>
---
 tools/testing/selftests/nolibc/Makefile.include | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/tools/testing/selftests/nolibc/Makefile.include 
b/tools/testing/selftests/nolibc/Makefile.include
index c30ca3a9ef14..ea520eac64a6 100644
--- a/tools/testing/selftests/nolibc/Makefile.include
+++ b/tools/testing/selftests/nolibc/Makefile.include
@@ -5,7 +5,7 @@ _CFLAGS_STACKPROTECTOR ?= $(call try-run, \
        echo 'void foo(void) {}' | $(CC) -x c - -o - -S $(CLANG_CROSS_FLAGS) 
$(__CFLAGS_STACKPROTECTOR) | grep -q __stack_chk_guard, \
        $(__CFLAGS_STACKPROTECTOR))
 _CFLAGS_SANITIZER ?= $(call cc-option,-fsanitize=undefined -fsanitize-trap=all)
-CFLAGS_NOLIBC_TEST  ?= -Os -fno-ident -fno-asynchronous-unwind-tables -std=c89 
\
+CFLAGS_NOLIBC_TEST  ?= -Os -fno-ident -fno-asynchronous-unwind-tables -std=c89 
-ggdb \
                -W -Wall -Wextra -Wundef -Wwrite-strings \
                $(call cc-option,-fno-stack-protector) $(call 
cc-option,-Wmissing-prototypes) \
                $(_CFLAGS_STACKPROTECTOR) $(_CFLAGS_SANITIZER)

---
base-commit: a3b2181459a2c74c03ddbad585f884eefc8ff8ff
change-id: 20260707-nolibc-debug-04c9cedd3eaf

Best regards,
--  
Thomas Weißschuh <[email protected]>


Reply via email to