[BL training-materials-updates] Update sysdev debugging lab to Ubuntu 18.04

[Michael Opdenacker]

Repository : git://git.free-electrons.com/training-materials.git
On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=2091a51ee4ab3249a5564d205856d792ec5ba60e

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

commit 2091a51ee4ab3249a5564d205856d792ec5ba60e
Author: Michael Opdenacker <michael.opdenacker at bootlin.com>
Date:   Fri Oct 5 07:30:33 2018 +0200

    Update sysdev debugging lab to Ubuntu 18.04
    
    Signed-off-by: Michael Opdenacker <michael.opdenacker at bootlin.com>


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

2091a51ee4ab3249a5564d205856d792ec5ba60e
 .../sysdev-application-debugging.tex                       | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)

diff --git a/labs/sysdev-application-debugging/sysdev-application-debugging.tex b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
index a588cad..15493b4 100644
--- a/labs/sysdev-application-debugging/sysdev-application-debugging.tex
+++ b/labs/sysdev-application-debugging/sysdev-application-debugging.tex
@@ -18,7 +18,7 @@ it looks like a a good idea to do your application debugging work
 with a {\em glibc} toolchain first, and then switch to lighter libraries
 once your application and software stack is production ready. 
 
-Extract the 2017.08.x sources into the current directory.
+Extract the Buildroot 2018.08 sources into the current directory.
 
 Then, in the \code{menuconfig} interface, configure the target
 architecture as done previously but configure the toolchain and
@@ -31,14 +31,14 @@ target packages differently:
    \item \code{Toolchain}: \code{Custom Toolchain}
    \item \code{Toolchain origin}: \code{Toolchain to be downloaded and installed}
    \item \code{Toolchain URL}:
-\code{https://toolchains.bootlin.com/downloads/releases/toolchains/armv7-eabihf/tarballs/armv7-eabihf--glibc--bleeding-edge-2017.08-rc2-5-g5c1b185-1.tar.bz2}\\
+\code{https://toolchains.bootlin.com/downloads/releases/toolchains/armv7-eabihf/tarballs/armv7-eabihf--glibc--bleeding-edge-2018.07-3.tar.bz2}\\
 	      You can easily choose such a toolchain on
 	      \url{https://toolchains.bootlin.com} by selecting the
 	      architecture, the C library and the compiler version you need. 
 	      While you can try with other versions, the above toolchain
 	      is known to make this lab work.
-   \item \code{External toolchain gcc version}: \code{7.x}
-   \item \code{External toolchain kernel headers series}: \code{4.9.x}
+   \item \code{External toolchain gcc version}: \code{8.x}
+   \item \code{External toolchain kernel headers series}: \code{4.14.x}
    \item \code{External toochain C library}: \code{glibc/eglibc}
    \item Select \code{Toolchain has SSP support?}
    \item Select \code{Toolchain has RPC support?}
@@ -58,7 +58,7 @@ target packages differently:
 Now, build your root filesystem.
 
 Go back to the \code{$HOME/embedded-linux-labs/debugging} directory
-and extract the \code{buildroot-2017.08.x/output/images/rootfs.tar}
+and extract the \code{buildroot-2018.08/output/images/rootfs.tar}
 archive in the \code{nfsroot} directory.
 
 Add this directory to the \code{/etc/exports} file and restart
@@ -81,7 +81,7 @@ you don't have the source code.
 Update the PATH:
 \footnotesize
 \begin{verbatim}
-export PATH=$HOME/embedded-linux-labs/debugging/buildroot-2017.08.x/output/host/bin:$PATH
+export PATH=$HOME/embedded-linux-labs/debugging/buildroot-2018.08/output/host/bin:$PATH
 \end{verbatim}
 \normalsize
 
@@ -155,7 +155,7 @@ variable (on one line):
 
 \begin{verbatim}
 (gdb) set sysroot /home/<user>/embedded-linux-labs/debugging/
-buildroot-2017.08.x/output/staging
+buildroot-2018.08/output/staging
 \end{verbatim}
 
 And tell \code{gdb} to connect to the remote system: