[bootlin/training-materials updates] master: C libraries: clarify ltrace limitations (47628a26)

[Michael Opdenacker]

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

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

commit 47628a26eb3be53e8ff0c04e264d2384296b5eba
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Thu Jan 27 16:12:43 2022 +0100

    C libraries: clarify ltrace limitations
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

47628a26eb3be53e8ff0c04e264d2384296b5eba
 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 135885d5..dcad410f 100644
--- a/slides/c-libraries/c-libraries.tex
+++ b/slides/c-libraries/c-libraries.tex
@@ -133,7 +133,8 @@ compare the size
   \begin{itemize}
   \item Advice to start developing and debugging your applications with
         {\em glibc}, which is the most standard solution, and is best
-        supported by debugging tools ({\em ltrace} for example).
+        supported by debugging tools ({\em ltrace} not supported by {\em
+        musl} in Buildroot, 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