Template:ArticleApprovedVersion
1. Article purpose[edit source]
This article provides useful information to start using Linux® tracing, monitoring and debugging environments.
Two entry points are proposed in this article:
- Linux tracing, monitoring and debugging tools, which gives an overview of some Linux® tools including usage and application domain. Template:Highlight.
- Trace and debug overview per Linux software frameworks, which points to articles explaining how to get trace and debug information about the Linux® software frameworks that are relevant for the STM32MPU Embedded Software. Template:Highlight.
2. Linux trace architecture overview[edit source]
The Linux® trace architecture can be organized into four levels as shown in the figure below (inspired by Brendan Gregg presentation[1]):
2.1. Back-end instrumentation[edit source]
The back-end instrumentation provides tracing sources built in the Linux® kernel. They are split into three categories:
- tracepoints: kernel static tracing, statically placed at logical places in the kernel. It provides key event details as a "format" string.
- kprobes: kernel dynamic tracing. It allows to trace function calls, returns and line numbers.
- uprobes: dynamic user-level tracing.
2.2. Tracing framework[edit source]
Also named tracers, they use tracing sources.
Tracing frameworks include kernel in-tree tracers such as ftrace and perf_events, and out-of-tree tracers such as SystemTap and sysdig.
2.3. Front-end tools[edit source]
Front-end tools come on top of tracers and help to configure them. For example:
- trace-cmd or LTTng for ftrace
- perf or perf-Tools for perf_events
2.4. Add-on tools and viewer[edit source]
Add-on tools are also on top of tracers. However, they are not embedded inside the Linux® kernel.
Viewer tools propose Visual interpretation of trace data. For example:
- kernelshark for ftrace/trace-cmd
- Trace Compass[2] for LTTng (and more)
- Flame Graph[3] for perf
3. Linux tracing, monitoring and debugging tools[edit source]
Linux® provides many tools that are either dedicated to one function or multifunction (generic).
They cover both Linux® kernel and Linux® user space.
3.1. Domain mapping[edit source]
The following mapping, done by Brendan Gregg [4], shows the different existing tools associated to the different Linux® frameworks. Template:ImageMap
3.2. Tool overview[edit source]
The following table provides a brief description of the tool, as well as its availability depending on the software packages:
Template:Y: this tool is either present (ready to use or to be activated), or can be integrated and activated on the software package.
Template:N: this tool is not present and cannot be integrated, or it is present but cannot be activated on the software package.
| Tool | STM32MPU Embedded Software distribution | STM32MPU Embedded Software distribution for Android™ | ||||||
|---|---|---|---|---|---|---|---|---|
| Name | Category | Purpose | Starter Package | Developer Package | Distribution Package | Starter Package | Developer Package | Distribution Package |
| blktrace | Tracing tools | blktrace[5] generates traces of the I/O traffic on block devices (SD card, USB, eMMC...) | Template:N | Template:Y | Template:Y | Template:UnderConstruction | ||
| systemd core dump | Debugging tools | systemd core dump: generates core dump files on Linux |
Template:Y | Template:N | Template:Y | Template:N | Template:N | Template:N |
| ethtool | Monitoring tools | ethtool[6] allows to query or control network driver and hardware settings, in particular for wired Ethernet devices. | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| ftrace | Tracing tools | ftrace[7] (Function Tracer) is a powerful kernel tracing utility that is able, for instance, to trace every kernel function calls and kernel events without adding any extra code in your kernel source code | Template:N | Template:N | Template:Y | Template:UnderConstruction | ||
| GDB | Debugging tools | The GNU Project debugger, GDB[8], allows monitoring program execution, or what the program was doing at the moment it crashed. |
Template:N* | Template:Y | Template:N** | Template:UnderConstruction | ||
| * Cross compile gdb binary is required and only available from Developer Package. ** It is recommended to use the Developer Package to run the gdb debug session, which provided all dependencies | ||||||||
| ifconfig | Monitoring tools | ifconfig[9] is a system administration utility for network interface configuration. Template:Warning |
Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| ip | Monitoring tools | ip[10] shows / manipulates routing, devices, policy routing and tunnels of network interfaces. |
Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| kmemleak | Monitoring tools | kmemleak[11] provides a means to detect possible kernel memory leaks in a similar way to a tracing garbage collector, with the difference that the orphan objects are not freed, but only reported via /sys/kernel/debug/kmemleak. It is Template:Highlight. |
Template:N | Template:Y | Template:Y | Template:UnderConstruction | ||
| trace-cmd | Tracing tools | trace-cmd[12] command interacts with the Ftrace tracer that is built inside the Linux kernel. It interfaces with the Ftrace specific files found in the debugfs file system under the tracing directory. kernelshark[13] is a front-end reader of trace-cmd output. "trace-cmd record" and "trace-cmd extract" create a trace.dat (trace-cmd.dat) file. kernelshark can read this file, and produce a graph and list view of the corresponding data. |
Template:N | Template:N | Template:Y | Template:UnderConstruction | ||
| ltrace | Tracing tools | ltrace[14] is used to display the calls to shared libraries made by a userspace application. ltrace is a userspace application. Its use is very similar to strace. |
Template:N | Template:N | Template:Y | Template:UnderConstruction | ||
| LTTng | Tracing tools | LTTng[15] is an open source tracing framework for Linux kernel and user spaces. It is a powerful tool that can be used for many purposes. LTTng traces need to be processed/displayed with a host tool such as Trace Compass[16], based on Eclipse plugin for increased portability. | Template:N | Template:N | Template:Y | Template:UnderConstruction | ||
| netdata | Monitoring tools | netdata[17] is a system for distributed real-time performance and health monitoring. It provides unparalleled insights, in real-time, of everything happening on the system it runs (including applications such as web and database servers), using modern interactive web dashboards. | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| netstat | Monitoring tools | netstat[18] prints network connections, routing tables, interface statistics, masquerade connections, and multicast membership information. | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| perf | Monitoring tools | perf[19] is a Linux user space tool, which allows getting system performance figures | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| strace | Tracing tools | strace[20] is able to intercept and record the system calls which are called by a process and the signals which are received by another process. | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| sysprof | Monitoring tools | sysprof[21] is a statistical, system-wide profiler for Linux. It helps in finding the functions in which a program spends most of its time. sysprof proposes a user interface available directly on the board display screen. |
Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| sysstat | Monitoring tools | The sysstat [22] tool suite contains utilities to monitor the system performance and usage activity. It contains various utilities, common to many commercial Unix distributions, as well as tools that can be scheduled (via a scheduler such as cron) to collect and historize performance and activity data:
|
Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| tcpdump | Monitoring tools | tcpdump[23] is a common packet analyzer that runs under the command line. It allows the user to display TCP/IP and other packets being transmitted or received over a network to which the computer is connected. | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| top | Monitoring tools | The top[24] program provides a dynamic real-time view of a running system. It can display system summary information as well as a list of tasks currently being managed by the Linux kernel. The types of system summary information shown and the types, order and size of information displayed for tasks are all user configurable and that configuration can be made persistent across restarts. (Extracted from man page[24]) | Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
| valgrind | Monitoring tools | valgrind[25] is an instrumentation framework for building dynamic analysis tools. Some Valgrind tools can automatically detect many memory management and threading bugs, and profile your programs in detail. This is tool for Linux application analysis. |
Template:Y | Template:Y | Template:Y | Template:UnderConstruction | ||
4. Trace and debug overview per Linux software frameworks[edit source]
The picture below allows accessing to different Linux software frameworks which provide specific trace and debug information in their Template:Highlight dedicated chapter.
5. Tips[edit source]
How to find Linux kernel driver associated to a device.
How to use the kernel dynamic debug.
6. Documentation and web articles[edit source]
A lot of articles on the web mention Linux® kernel tracing and profiling. The following links provide a good introduction to these topics:
- Linux Performance Analysis - New Tools and Old Secrets: description of the Linux® technology and of the different tools available.
- Yocto project: Tracing and profiling: How to enable tracing and profiling tools using Yocto
- Brendan Gregg Linux performance page
Reference list:
- ↑ http://www.brendangregg.com/linuxperf.html
- ↑ http://www.tracecompass.org
- ↑ http://www.brendangregg.com/flamegraphs.html
- ↑ http://www.brendangregg.com/linuxperf.html
- ↑ https://linux.die.net/man/8/blktrace
- ↑ https://linux.die.net/man/8/ethtool
- ↑ https://elinux.org/Ftrace
- ↑ https://www.gnu.org/software/gdb
- ↑ https://linux.die.net/man/8/ifconfig
- ↑ https://linux.die.net/man/8/ip
- ↑ http://www.procode.org/kmemleak/
- ↑ https://lwn.net/Articles/410200/
- ↑ http://rostedt.homelinux.com/kernelshark
- ↑ https://www.ltrace.org/
- ↑ http://lttng.org
- ↑ http://tracecompass.org/
- ↑ https://my-netdata.io
- ↑ https://linux.die.net/man/8/netstat
- ↑ https://perf.wiki.kernel.org/index.php/Main_Page
- ↑ https://strace.io/
- ↑ http://www.sysprof.com/
- ↑ http://sebastien.godard.pagesperso-orange.fr/
- ↑ http://www.tcpdump.org/
- ↑ Jump up to: 24.0 24.1 http://linux.die.net/man/1/top
- ↑ http://valgrind.org/