[bootlin/training-materials updates] master: debugging course: minor fixes (c074f8d5)
Michael Opdenacker
michael.opdenacker at bootlin.com
Mon Nov 28 12:23:50 CET 2022
Repository : https://github.com/bootlin/training-materials
On branch : master
Link : https://github.com/bootlin/training-materials/commit/c074f8d58d4a73e60b6606a174b5430297c28c7a
>---------------------------------------------------------------
commit c074f8d58d4a73e60b6606a174b5430297c28c7a
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date: Mon Nov 28 12:23:50 2022 +0100
debugging course: minor fixes
Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>
>---------------------------------------------------------------
c074f8d58d4a73e60b6606a174b5430297c28c7a
.../debugging-linux-application-stack.tex | 8 ++++----
slides/debugging-principles/debugging-principles.tex | 4 ++--
2 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex b/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex
index 45c1053a..ef431667 100644
--- a/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex
+++ b/slides/debugging-linux-application-stack/debugging-linux-application-stack.tex
@@ -11,7 +11,7 @@
\item Might be named differently between architectures but the goal is
the same
\end{itemize}
- \item Allow the kernel to control the full processor state (handle
+ \item Allows the kernel to control the full processor state (handle
exceptions, MMU, etc) whereas the userspace can only do basic control
and execute under the kernel supervision.
\end{itemize}
@@ -23,7 +23,7 @@
\item A process is a group of resources that are allocated by the operating
to allow the execution of a program.
\begin{itemize}
- \item memory regions, threads, files, etc.
+ \item Memory regions, threads, files, etc.
\end{itemize}
\item A process is identified by a PID ({\bf P}rocess {\bf ID}) and all the
information that are specific to this process are exposed in
@@ -44,7 +44,7 @@
\begin{frame}
\frametitle{Processes and Threads (2/2)}
\begin{itemize}
- \item Threads are independent execution unit that are sharing common
+ \item Threads are independent execution units that are sharing common
resources inside a process.
\begin{itemize}
\item Same address space, file descriptors, etc.
@@ -108,7 +108,7 @@
\begin{frame}
\frametitle{Userspace/Kernel memory layout}
- Multiple processes have different user memory space
+ Multiple processes have different user memory spaces
\center\includegraphics[height=0.7\textheight]{slides/debugging-linux-application-stack/multiple_process.pdf}
\end{frame}
diff --git a/slides/debugging-principles/debugging-principles.tex b/slides/debugging-principles/debugging-principles.tex
index 3a7a2f32..498c1114 100644
--- a/slides/debugging-principles/debugging-principles.tex
+++ b/slides/debugging-principles/debugging-principles.tex
@@ -50,7 +50,7 @@
\begin{itemize}
\item Using {\em perf}, {\em OProfile} for instance.
\end{itemize}
- \item First step consist in gathering data from program execution
+ \item First step consists in gathering data from program execution
\begin{itemize}
\item Function call count, memory usage, CPU load, cache miss, etc
\end{itemize}
@@ -77,7 +77,7 @@
\begin{itemize}
\item Implies a large amount of recorded data since the complete execution
trace is recorded
- \item often bigger overhead than profiling.
+ \item Often bigger overhead than profiling.
\end{itemize}
\item Can also be used for debugging purpose since data can be extracted
with tracepoints.
More information about the training-materials-updates
mailing list