[bootlin/training-materials updates] master: debugging: labs: gdb: add pro tip on gdb p command (bd73fc78)

[Clément Léger]

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

>---------------------------------------------------------------

commit bd73fc78e110fb1229664a84e7a77fb75749a557
Author: Clément Léger <clement.leger at bootlin.com>
Date:   Thu Nov 17 13:09:04 2022 +0100

    debugging: labs: gdb: add pro tip on gdb p command
    
    Signed-off-by: Clément Léger <clement.leger at bootlin.com>


>---------------------------------------------------------------

bd73fc78e110fb1229664a84e7a77fb75749a557
 labs/debugging-application-crash/debugging-application-crash.tex | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/labs/debugging-application-crash/debugging-application-crash.tex b/labs/debugging-application-crash/debugging-application-crash.tex
index 8120064c..294c2620 100644
--- a/labs/debugging-application-crash/debugging-application-crash.tex
+++ b/labs/debugging-application-crash/debugging-application-crash.tex
@@ -59,6 +59,10 @@ Then continue the execution and try to find the error using GDB. There are
 multiple ways to debug such program. We will track down up to the error in order
 to understand
 
+{\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
+\code{display_linked_list()}.}
+
 \section{Using a coredump with GDB}
 
 Sometimes, the problems only arise in production and you can only gather data