debugging: labs: clarify sentence

Signed-off-by: Luca Ceresoli <[email protected]>

labs/debugging-kernel-debugging/debugging-kernel-debugging.tex

@@ -126,10 +126,11 @@ \subsection{Locating the exact line where the error happens}
 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: