app/debugging: remove trailing whitespaces

Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>

1 files changed, 14 insertions, 14 deletions

diff --git a/application-devel/debugging-tools/pres_debugging-tools_en.tex b/application-devel/debugging-tools/pres_debugging-tools_en.tex
index 4adf4f8..7fc8501 100644
--- a/application-devel/debugging-tools/pres_debugging-tools_en.tex
+++ b/application-devel/debugging-tools/pres_debugging-tools_en.tex
@@ -57,7 +57,7 @@ gdb ./hello
 run the program
 \begin{verbatim}
 (gdb) run
-Starting program: /home/devel/work/hello 
+Starting program: /home/devel/work/hello
 Hello, world!
 
 [Inferior 1 (process 935) exited normally]
@@ -87,7 +87,7 @@ Breakpoint 1 at 0x400528: file hello.c, line 5.
 run the program again (now with breakpoint set)
 \begin{verbatim}
 (gdb) run
-Starting program: /home/jan/work/examples/hello 
+Starting program: /home/jan/work/examples/hello
 
 Breakpoint 1, main () at hello.c:5
 5               printf("Hello, world!\n");
@@ -100,7 +100,7 @@ Hello, world!
 \end{verbatim}
 let the program run to end
 \begin{verbatim}
-(gdb) continue 
+(gdb) continue
 Continuing.
 [...]
 \end{verbatim}
@@ -173,12 +173,12 @@ $ ulimit -c unlimited
 \end{verbatim}
 run program
 \begin{verbatim}
-$ ./hello_segfault 
+$ ./hello_segfault
 Segmentation fault (core dumped)
 \end{verbatim}
 core file created
 \begin{verbatim}
-$ ls -l core 
+$ ls -l core
 -rw------- 1 devel devel 249856 Jan 1 00:00 core
 \end{verbatim}
 \end{frame}
@@ -294,7 +294,7 @@ Program terminated with signal SIGSEGV, Segmentation fault.
 \end{alertblock}
 verify that the debug symbols match the executable
 \begin{verbatim}
-$ file hello_crash hello_crash.dbg 
+$ file hello_crash hello_crash.dbg
 hello_crash:     ... BuildID[sha1]=9bc82e1d6627ba58492ea24462fd6658726c4fc0
 hello_crash.dbg: ... BuildID[sha1]=9bc82e1d6627ba58492ea24462fd6658726c4fc0
 \end{verbatim}
@@ -348,7 +348,7 @@ Hello, world!
 \frametitle{Remote Debugging Session}
 from the target:
 \begin{verbatim}
-$ gdbserver :2345 ./hello 
+$ gdbserver :2345 ./hello
 Process ./hello created; pid = 310
 Listening on port 2345
 \end{verbatim}
@@ -577,11 +577,11 @@ $ valgrind --leak-check=full ./mem_leak
 ==8457== HEAP SUMMARY:
 ==8457==     in use at exit: 49 bytes in 49 blocks
 ==8457==   total heap usage: 50 allocs, 1 frees, 50 bytes allocated
-==8457== 
+==8457==
 ==8457== 49 bytes in 49 blocks are definitely lost in loss record 1 of 1
 ==8457==    at 0x4C28C20: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
 ==8457==    by 0x4005C4: main (mem_leak.c:14)
-==8457== 
+==8457==
 ==8457== LEAK SUMMARY:
 ==8457==    definitely lost: 49 bytes in 49 blocks
 [...]
@@ -598,17 +598,17 @@ $ valgrind --leak-check=full ./array_access
 ==8493==  Address 0x51e0068 is 0 bytes after a block of size 40 alloc'd
 ==8493==    at 0x4C2AD10: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
 ==8493==    by 0x4005AC: main (array_access.c:10)
-==8493== 
-0 0 0 0 0 0 0 0 0 0 0 
-==8493== 
+==8493==
+0 0 0 0 0 0 0 0 0 0 0
+==8493==
 ==8493== HEAP SUMMARY:
 ==8493==     in use at exit: 40 bytes in 1 blocks
 ==8493==   total heap usage: 1 allocs, 0 frees, 40 bytes allocated
-==8493== 
+==8493==
 ==8493== 40 bytes in 1 blocks are definitely lost in loss record 1 of 1
 ==8493==    at 0x4C2AD10: calloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
 ==8493==    by 0x4005AC: main (array_access.c:10)
-==8493== 
+==8493==
 ==8493== LEAK SUMMARY:
 ==8493==    definitely lost: 40 bytes in 1 blocks
 [...]