[bootlin/training-materials updates] master: debugging: labs: remove redundant commands (51bf5eb7)

Luca Ceresoli luca.ceresoli at bootlin.com
Thu Aug 24 21:57:44 CEST 2023


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

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

commit 51bf5eb7eb6f96d91bf102d4be826833e4921a0a
Author: Luca Ceresoli <luca.ceresoli at bootlin.com>
Date:   Wed Aug 23 17:57:52 2023 +0200

    debugging: labs: remove redundant commands
    
    These commands are the same as a few lines above, so avoid duplication.
    
    Signed-off-by: Luca Ceresoli <luca.ceresoli at bootlin.com>


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

51bf5eb7eb6f96d91bf102d4be826833e4921a0a
 .../debugging-application-profiling.tex                          | 9 +--------
 1 file changed, 1 insertion(+), 8 deletions(-)

diff --git a/labs/debugging-application-profiling/debugging-application-profiling.tex b/labs/debugging-application-profiling/debugging-application-profiling.tex
index 597cdb8b..f566ef8b 100644
--- a/labs/debugging-application-profiling/debugging-application-profiling.tex
+++ b/labs/debugging-application-profiling/debugging-application-profiling.tex
@@ -164,14 +164,7 @@ $ perf record --call-graph dwarf ./png_convert tux_small.png out.png
 We specify that we want to record the call graph using the DWARF information
 that are contained in ELF file (compiled with \code{-g}). Once recorded, on the
 desktop platform, display the results with \code{perf report} and compare them
-with callgrind ones on your development platform:
-
-\begin{bashinput}
-$ sudo chown $USER:$USER perf.data
-$ export CROSS_COMPILE=/home/$USER/debugging-labs/buildroot/output/host/bin/arm-linux-
-$ perf report --symfs=/home/$USER/debugging-labs/buildroot/output/staging/
-   -k /home/$USER/debugging-labs/buildroot/output/build/linux-5.13/vmlinux
-\end{bashinput}
+with callgrind ones on your development platform.
 
 {\em NOTE: the vmlinux file used for the \code{-k} option must match the kernel
 build id that is running on the board or perf will not use it.}




More information about the training-materials-updates mailing list