[FE training-materials-updates] kernel-debugging.tex: font improvements
Michael Opdenacker
michael.opdenacker at free-electrons.com
Wed Oct 3 07:58:59 CEST 2012
Repository : git://git.free-electrons.com/training-materials.git
On branch : master
Link : http://git.free-electrons.com/training-materials/commit/?id=4a47c7f12048ddd2cb614c7de8c53898b4d1faf4
>---------------------------------------------------------------
commit 4a47c7f12048ddd2cb614c7de8c53898b4d1faf4
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date: Wed Oct 3 07:01:34 2012 +0200
kernel-debugging.tex: font improvements
>---------------------------------------------------------------
4a47c7f12048ddd2cb614c7de8c53898b4d1faf4
labs/kernel-debugging/kernel-debugging.tex | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/labs/kernel-debugging/kernel-debugging.tex b/labs/kernel-debugging/kernel-debugging.tex
index 8e20ec2..594a505 100644
--- a/labs/kernel-debugging/kernel-debugging.tex
+++ b/labs/kernel-debugging/kernel-debugging.tex
@@ -2,7 +2,7 @@
analysis}{Objective: Use kernel debugging mechanisms and analyze a
kernel crash}
-\section{{\tt pr\_debug()} and dynamic debugging}
+\section{pr\_debug() and dynamic debugging}
Add a \code{pr_debug()} call in the \code{write()} operation that shows
each character being written (or its hexadecimal representation) and
@@ -15,8 +15,8 @@ that you added? Your kernel probably does not have
\code{DEBUG} defined., so you shouldn't see any message.
Now, recompile your kernel with \code{CONFIG_DYNAMIC_DEBUG} and reboot. The
-dynamic debug feature can be configured using debugfs, so you'll have
-to mount the debugfs filesystem first. Then, after reading the dynamic
+dynamic debug feature can be configured using \code{debugfs}, so you'll have
+to mount the \code{debugfs} filesystem first. Then, after reading the dynamic
debug documentation in the kernel sources, do the following things:
\begin{itemize}
@@ -38,15 +38,15 @@ drivers and be able to selectively enable only some of them.
\section{debugfs}
Since you have enabled debugfs to control the dynamic debug feature,
-we will also use it to add a new debugfs entry. Modify your driver to
+we will also use it to add a new \code{debugfs} entry. Modify your driver to
add:
\begin{itemize}
-\item A directory called \code{serial} in the {\em debugfs} filesystem
+\item A directory called \code{serial} in the \code{debugfs} filesystem
\item And file called \code{counter} inside the \code{serial}
- directory of the debugfs filesystem. This file should allow to see
+ directory of the \code{debugfs} filesystem. This file should allow to see
the contents of the \code{counter} variable of your module.
\end{itemize}
@@ -67,12 +67,12 @@ Make sure that your kernel has the following options enabled:
\item Support for root filesystem over NFS support
-\item The \code{CONFIG_DEBUG_INFO} configuration option, (Kernel
- Hacking section) which makes it possible to see source code in the
- disassembled kernel
+\item The \code{CONFIG_DEBUG_INFO} configuration option,
+ (\code{Kernel Hacking} section) which makes it possible to see source
+ code in the disassembled kernel.
\item Disable the \code{CONFIG_ARM_UNWIND} configuration option
- (Kernel Hacking section). This option enables a new mechanism to
+ (\code{Kernel Hacking} section). This option enables a new mechanism to
handle stack backtraces, but this new mechanism is not yet as
functional and reliable as the old mechanism based on frame
pointers. In our case, with our board, you get a backtrace only if
More information about the training-materials-updates
mailing list