[bootlin/training-materials updates] master: debugging: labs: clarify sentence (f4c672da)

Luca Ceresoli luca.ceresoli at bootlin.com
Fri Nov 17 13:56:49 CET 2023


Repository : https://github.com/bootlin/training-materials
On branch  : master
Link       : https://github.com/bootlin/training-materials/commit/f4c672da0f38fa3016752792c33c73979da0d2c2

>---------------------------------------------------------------

commit f4c672da0f38fa3016752792c33c73979da0d2c2
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Fri Nov 17 13:56:49 2023 +0100

    debugging: labs: clarify sentence
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


>---------------------------------------------------------------

f4c672da0f38fa3016752792c33c73979da0d2c2
 labs/debugging-kernel-debugging/debugging-kernel-debugging.tex | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
index 81495e53..b80dc46f 100644
--- a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -126,10 +126,11 @@ If you look again, the report tells you at what offset in the function
 this happens. We will disassemble the code for this function to understand
 exactly where the issue happened.
 
-That is where we need a kernel compiled with \kconfig{CONFIG_DEBUG_INFO}
-as we did in the initial lab. This way, the kernel vmlinux file is
-compiled with \code{-g} compiler flag, which adds a lot of debugging
-information (matching between source code lines and assembly for instance).
+That is where we need a kernel compiled with \kconfig{CONFIG_DEBUG_INFO},
+which is already enabled in the kernel we compiled in the initial lab.
+This way, the kernel vmlinux file is compiled with \code{-g} compiler flag,
+which adds a lot of debugging information (matching between source code
+lines and assembly for instance).
 
 Using \code{addr2line}, find the exact source code line were the crash happened.
 For that, you can use the following command on your development host:




More information about the training-materials-updates mailing list