From 39fcd92210599f903566fc914ba31f67b6c4f758 Mon Sep 17 00:00:00 2001
From: Andreas Kling <awesomekling@gmail.com>
Date: Fri, 8 Nov 2019 17:36:29 +0100
Subject: [PATCH] Kernel: Remove debug spam about dump_backtrace() calling
 itself

This was too noisy and important-sounding, when it doesn't really
matter that much. It's not the end of the world if symbolication fails
for one reason or another.
---
 Kernel/KSyms.cpp | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/Kernel/KSyms.cpp b/Kernel/KSyms.cpp
index 9611aa096f..949e11c143 100644
--- a/Kernel/KSyms.cpp
+++ b/Kernel/KSyms.cpp
@@ -134,10 +134,8 @@ static void load_ksyms_from_data(const ByteBuffer& buffer)
 void dump_backtrace()
 {
     static bool in_dump_backtrace = false;
-    if (in_dump_backtrace) {
-        dbgprintf("dump_backtrace() called from within itself, what the hell is going on!\n");
+    if (in_dump_backtrace)
         return;
-    }
     TemporaryChange change(in_dump_backtrace, true);
     TemporaryChange disable_kmalloc_stacks(g_dump_kmalloc_stacks, false);
     u32 ebp;