[bootlin/training-materials updates] master: C libraries: glibc is better for debugging tools too (d3d7ac41)

[Michael Opdenacker]

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

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

commit d3d7ac414c500eedb61bb18f2f439e482707eef0
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Tue Jan 25 10:49:19 2022 +0100

    C libraries: glibc is better for debugging tools too
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

d3d7ac414c500eedb61bb18f2f439e482707eef0
 slides/c-libraries/c-libraries.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/slides/c-libraries/c-libraries.tex b/slides/c-libraries/c-libraries.tex
index 944e67dd..135885d5 100644
--- a/slides/c-libraries/c-libraries.tex
+++ b/slides/c-libraries/c-libraries.tex
@@ -132,7 +132,8 @@ compare the size
   \frametitle{Advise for choosing the C library}
   \begin{itemize}
   \item Advice to start developing and debugging your applications with
-        {\em glibc}, which is the most standard solution.
+        {\em glibc}, which is the most standard solution, and is best
+        supported by debugging tools ({\em ltrace} for example).
   \item Then, when everything works, if you have size constraints, try to compile
         your app and then the entire filesystem with {\em uClibc} or {\em musl}.
   \item If you run into trouble, it could be because of missing features