From f487a2e31258aae56304b947950355ac2b074f2f Mon Sep 17 00:00:00 2001 From: Ben Pfaff Date: Thu, 18 May 2006 19:47:22 +0000 Subject: [PATCH] Wording. --- doc/debug.texi | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/debug.texi b/doc/debug.texi index 27d4f26..62d951a 100644 --- a/doc/debug.texi +++ b/doc/debug.texi @@ -118,7 +118,7 @@ Alternatively, it could be that the @file{kernel.o} you passed to @command{backtrace} is not the same kernel that produced the backtrace. -Sometimes backtraces can be confusing without implying corruption. +Sometimes backtraces can be confusing without any corruption. Compiler optimizations can cause surprising behavior. When a function has called another function as its final action (a @dfn{tail call}), the calling function may not appear in a backtrace at all. Similarly, when -- 2.30.2