Skip to content

Commit bf73133

Browse files
committedFeb 24, 2025·
debugging: slides: remove italic from slide titles
There are many slides titles which have some parts in italic, likely to try to highlight software components or commands, but it does not bring much, and this practice is not homogeneous among all slides. Get rid of italic in slides titles everywhere to make slides titles consistent. Signed-off-by: Alexis Lothoré <alexis.lothore@bootlin.com>
1 parent 9152df0 commit bf73133

File tree

5 files changed

+45
-45
lines changed

5 files changed

+45
-45
lines changed
 

‎slides/debugging-application-profiling/debugging-application-profiling.tex

+4-4
Original file line numberDiff line numberDiff line change
@@ -298,7 +298,7 @@ \subsection{Execution profiling}
298298
\end{frame}
299299

300300
\begin{frame}[fragile]
301-
\frametitle{{\em perf stat} example (1/2)}
301+
\frametitle{perf stat example (1/2)}
302302
\begin{block}{}
303303
\begin{minted}[fontsize=\tiny]{console}
304304
$ perf stat convert foo.png foo.jpg
@@ -330,7 +330,7 @@ \subsection{Execution profiling}
330330
\end{frame}
331331
332332
\begin{frame}[fragile]
333-
\frametitle{{\em perf stat} example (2/2)}
333+
\frametitle{perf stat example (2/2)}
334334
\begin{itemize}
335335
\item List all events:
336336
\end{itemize}
@@ -364,7 +364,7 @@ \subsection{Execution profiling}
364364
\end{frame}
365365
366366
\begin{frame}[fragile]
367-
\frametitle{{\em Cachegrind}}
367+
\frametitle{Cachegrind}
368368
\begin{itemize}
369369
\item {\em Cachegrind} is a tool provided by {\em valgrind} for
370370
profiling program interactions with the instruction and data cache hierarchy.
@@ -395,7 +395,7 @@ \subsection{Execution profiling}
395395
\end{frame}
396396
397397
\begin{frame}[fragile]
398-
\frametitle{{\em Callgrind}}
398+
\frametitle{Callgrind}
399399
\begin{itemize}
400400
\item Provided by {\em valgrind} and allowing to profile an application call graph
401401
(user-space only).

‎slides/debugging-application-tracing/debugging-application-tracing.tex

+4-4
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ \subsection{LD\_PRELOAD}
5454
\end{frame}
5555

5656
\begin{frame}[fragile]
57-
\frametitle{{\em LD\_PRELOAD} example 1/2}
57+
\frametitle{LD\_PRELOAD example 1/2}
5858
\begin{itemize}
5959
\item Library snippet that we want to preload using {\em LD\_PRELOAD}:
6060
\end{itemize}
@@ -89,7 +89,7 @@ \subsection{LD\_PRELOAD}
8989
\end{frame}
9090

9191
\begin{frame}[fragile]
92-
\frametitle{{\em LD\_PRELOAD} example 2/2}
92+
\frametitle{LD\_PRELOAD example 2/2}
9393
\begin{itemize}
9494
\item Chaining a call to the real symbol to avoid altering the
9595
application behavior:
@@ -171,7 +171,7 @@ \subsection{uprobes and perf}
171171
\end{frame}
172172

173173
\begin{frame}[fragile]
174-
\frametitle{The {\em perf} tool}
174+
\frametitle{The perf tool}
175175
\begin{itemize}
176176
\item {\em perf} tool was started as a tool to profile application under
177177
Linux using performance counters (\manpage{perf}{1}).
@@ -189,7 +189,7 @@ \subsection{uprobes and perf}
189189
\end{frame}
190190

191191
\begin{frame}[fragile]
192-
\frametitle{Using {\em perf record}}
192+
\frametitle{Using perf record}
193193
\begin{itemize}
194194
\item {\em perf record} allows to record performance events per-thread,
195195
per-process and per-cpu basis.

‎slides/debugging-common-tools/debugging-common-tools.tex

+3-3
Original file line numberDiff line numberDiff line change
@@ -202,7 +202,7 @@ \subsection{ELF file analysis}
202202

203203

204204
\begin{frame}[fragile]
205-
\frametitle{{\em ldd}}
205+
\frametitle{ldd}
206206
\begin{itemize}
207207
\item In order to display the shared libraries used by an ELF binary, one
208208
can use {\em ldd} (Generally packaged with C library. See \manpage{ldd}{1}).
@@ -276,7 +276,7 @@ \subsection{Process and CPU monitoring tools}
276276
\end{frame}
277277
278278
\begin{frame}[fragile]
279-
\frametitle{{\em ps} example}
279+
\frametitle{ps example}
280280
\begin{itemize}
281281
\frametitle{Processes with {\em ps}}
282282
\item Display all processes in a friendly way:
@@ -355,7 +355,7 @@ \subsection{Process and CPU monitoring tools}
355355
\subsection{Memory monitoring tools}
356356

357357
\begin{frame}[fragile]
358-
\frametitle{{\em free}}
358+
\frametitle{free}
359359
\begin{itemize}
360360
\item {\em free} is a simple program that displays the amount of free and
361361
used memory in the system (\manpage{free}{1}).

‎slides/debugging-kernel-debugging/debugging-kernel-debugging.tex

+9-9
Original file line numberDiff line numberDiff line change
@@ -275,7 +275,7 @@ \subsection{Built-in kernel self tests}
275275
\end{frame}
276276

277277
\begin{frame}
278-
\frametitle{{\em KASAN}}
278+
\frametitle{KASAN}
279279
\begin{itemize}
280280
\item Kernel Address Space Sanitizer
281281
\item Allows to find use-after-free and out-of-bounds memory accesses
@@ -293,7 +293,7 @@ \subsection{Built-in kernel self tests}
293293
\end{frame}
294294

295295
\begin{frame}
296-
\frametitle{{\em Kmemleak}}
296+
\frametitle{Kmemleak}
297297
\begin{itemize}
298298
\item Kmemleak allows to find memory leaks for dynamically allocated objects
299299
with \code{kmalloc()}
@@ -320,7 +320,7 @@ \subsection{Built-in kernel self tests}
320320
\end{frame}
321321

322322
\begin{frame}[fragile]
323-
\frametitle{{\em Kmemleak} report}
323+
\frametitle{Kmemleak report}
324324
\begin{block}{}
325325
\begin{minted}[fontsize=\small]{console}
326326
# cat /sys/kernel/debug/kmemleak
@@ -344,7 +344,7 @@ \subsection{Built-in kernel self tests}
344344
\end{frame}
345345

346346
\begin{frame}
347-
\frametitle{{\em UBSAN}}
347+
\frametitle{UBSAN}
348348
\begin{itemize}
349349
\item UBSAN is a runtime checker for code with undefined behavior
350350
\begin{itemize}
@@ -366,7 +366,7 @@ \subsection{Built-in kernel self tests}
366366
\end{frame}
367367

368368
\begin{frame}[fragile]
369-
\frametitle{{\em UBSAN}: example of UBSAN report}
369+
\frametitle{UBSAN: report example}
370370
\begin{itemize}
371371
\item Report for an undefined behavior due to a shift with a value > 32.
372372
\end{itemize}
@@ -466,7 +466,7 @@ \subsection{KGDB}
466466
\end{frame}
467467
468468
\begin{frame}
469-
\frametitle{{\em KDB}}
469+
\frametitle{KDB}
470470
\begin{itemize}
471471
\item \kconfig{CONFIG_KGDB_KDB} includes a kgdb frontend name "KDB"
472472
\item This frontend exposes a debug prompt on the serial console which
@@ -503,7 +503,7 @@ \subsection{KGDB}
503503
\end{frame}
504504
505505
\begin{frame}[fragile]
506-
\frametitle{{\em kdmx}}
506+
\frametitle{kdmx}
507507
\begin{itemize}
508508
\item When the system has only a single serial port, it is not possible to
509509
use both KGDB and the serial line as an output terminal since only one
@@ -553,7 +553,7 @@ \subsection{KGDB}
553553
\subsection{crash}
554554
555555
\begin{frame}
556-
\frametitle{{\em crash}}
556+
\frametitle{crash}
557557
\begin{itemize}
558558
\item {\em crash} is a CLI tool allowing to investigate kernel (dead or
559559
alive!)
@@ -574,7 +574,7 @@ \subsection{crash}
574574
\end{frame}
575575
576576
\begin{frame}[fragile]
577-
\frametitle{{\em crash} example}
577+
\frametitle{crash example}
578578
\begin{itemize}
579579
\begin{block}{}
580580
\begin{minted}[fontsize=\tiny]{console}

0 commit comments

Comments
 (0)
Please sign in to comment.