[bootlin/training-materials updates] master: debugging: labs: fix space before exclamation mark (bf229e83)
Luca Ceresoli
luca.ceresoli at bootlin.com
Mon Mar 27 14:47:01 CEST 2023
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/bf229e832da4d642645feb88e9ae8d3d5375901a
>---------------------------------------------------------------
commit bf229e832da4d642645feb88e9ae8d3d5375901a
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date: Mon Mar 27 14:44:26 2023 +0200
debugging: labs: fix space before exclamation mark
In English there must be no space before ending punctuation.
Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>
>---------------------------------------------------------------
bf229e832da4d642645feb88e9ae8d3d5375901a
labs/debugging-application-crash/debugging-application-crash.tex | 4 ++--
labs/debugging-kernel-debugging/debugging-kernel-debugging.tex | 8 ++++----
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/labs/debugging-application-crash/debugging-application-crash.tex b/labs/debugging-application-crash/debugging-application-crash.tex
index 5ef57107..881045b8 100644
--- a/labs/debugging-application-crash/debugging-application-crash.tex
+++ b/labs/debugging-application-crash/debugging-application-crash.tex
@@ -37,7 +37,7 @@ the file.
$ ./linked_list
\end{bashinput}
-From what you can see, it actually crashes ! So we will use GDB to debug that
+From what you can see, it actually crashes! So we will use GDB to debug that
program. We will do that remotely since our target does not embed a full gdb,
only a gdbserver, a lightweight gdb server that allows connecting with a remote
full feature GDB. Start our program using gdbserver in multi mode:
@@ -69,7 +69,7 @@ in a \code{~/.gdbinit} file. For instance, history can be enabled with
switch from the command line to the TUI view using Ctrl X + O.}
{\em TIP: in gdb, not only values can be displayed using \code{p} command but
-functions can also be called directly from gdb ! Try to call
+functions can also be called directly from gdb! Try to call
\code{display_linked_list()}.}
{\em NOTE: you can exit gdbserver from the connected gdb process using the
diff --git a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
index 6f7aa56a..c4fe91b3 100644
--- a/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
+++ b/labs/debugging-kernel-debugging/debugging-kernel-debugging.tex
@@ -86,7 +86,7 @@ pointer addresses. To do so, use the following command on the target:
You can use \code{addr2line} to identify the location in source code of the
lines that did cause the reports. You will also notice other memory leaks that
-are actually some real memory leaks that did exist in the 5.13 kernel version !
+are actually some real memory leaks that did exist in the 5.13 kernel version!
\section{OOPS analysis}
We noticed that the watchdog command generated a crash on the kernel. In order
@@ -97,7 +97,7 @@ $ watchdog -T 10 -t 5 /dev/watchdog0
\end{bashinput}
Immediatly after executing this commands, you'll see that the kernel will report
-an OOPS !
+an OOPS!
\subsection{Analyzing the crash message}
@@ -109,7 +109,7 @@ stack is.
Using Elixir (\url{https://elixir.bootlin.com/linux/latest/source}) or the
kernel source code, have a look at the definition of this function. In most
cases, a careful review of the driver source code is enough to understand the
-issue. But not in that case !
+issue. But not in that case!
\subsection{Locating the exact line where the error happens}
@@ -174,7 +174,7 @@ Use <ctrl>C to terminate program
Note: the slave ports number will depend on the run.
\textbf{Important: before using \code{/dev/pts/7} and \code{/dev/pts/8}, the
-picocom process that did opened \code{/dev/ttyACM0} must be closed !}
+picocom process that did opened \code{/dev/ttyACM0} must be closed!}
On the target, setup KGDB by setting the console to be used for that purpose in
kgdboc module parameters:
More information about the training-materials-updates
mailing list