[bootlin/training-materials updates] master: labs/kernel-debugging: fix section/subsection (b0bf45e5)

Thomas Petazzoni thomas.petazzoni at bootlin.com
Tue May 18 12:03:40 CEST 2021

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


commit b0bf45e58ae8fa0195b20667129cd12483779960
Author: Thomas Petazzoni <thomas.petazzoni at bootlin.com>
Date:   Tue May 18 12:03:40 2021 +0200

    labs/kernel-debugging: fix section/subsection
    Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com>


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

diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index da914f60..a2872915 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -82,7 +82,7 @@ Go to the \code{~/linux-kernel-labs/modules/nfsroot/root/debugging/} directory.
 Compile the \code{drvbroken} in this directory, and load it on your
 board. See it crashing in a nice way.
-\section{Analyzing the crash message}
+\subsection{Analyzing the crash message}
 Analyze the crash message carefully. Knowing that on ARM, the \code{PC}
 register contains the location of the instruction being executed, find
@@ -93,7 +93,7 @@ Using Elixir or the kernel source code, have a look at the definition of this
 function. This, with a careful review of the driver source code should
 probably be enough to help you understand and fix the issue.
-\section{Locating the exact line where the error happens}
+\subsection{Locating the exact line where the error happens}
 Even if you already found out which instruction caused the crash, it's
 useful to use information in the crash report.

More information about the training-materials-updates mailing list