Debugging Linux Kernel using SystemTap Part1 - What, Purpose, Installation, Working, Hello World

-
What is SystemTap?

 SystemTap is command line utility which allows kernel developers to investigate the behavior of the kernel and user-space applications.

In order to debug or analyze kernel space, developers need to modify, compile, install and reboot. With SystemTap, you can debug the kernel without the need to rebuild and install.

What is the purpose of SystemTap?

SystemTap provides a powerful way for understanding what logic is happening and what variables and memory locations are changing. Used when there is no interactive debugger.

Main purpose of SystemTap is to trace events. Examples of events:

  • Function Entering and Exiting
  • Timer Expiring
  • Network Packet Reception
Whenever any registered events occur, SystemTap calls the user handler, which can collect and display
  • Function Parameters
  • Values of Variables
  • Contents of Memory Locations
  • etc
Installation of SystemTap:

It's better we install SystemTap from source code, as I faced a lot of issues when I issued apt-get to install systemtap.

Steps for installing SystemTap from Source Code:

1.  wget https://sourceware.org/systemtap/ftp/releases/systemtap-4.0.tar.gz
2.  tar xzvf systemtap-4.0.tar.gz
3.  cd systemtap-4.0/ &&          ./configure &&          make all;
4. sudo make install

When you install, you will get stap and staprun utility

How Stap Works?

Stap internally uses KProbes and loadable modules to dynamically add probe points and newly generated code to the running kernel.

When you run stap <script.stp>

1. Translates the .stp file into Kernel Module (C code)
2. Compiles C Code to module (.ko file)
3. Loads the module into the kernel
4. Module runs, reporting events of interest as specified by the script.
5. Information is collected and stap reports it to stdout
6. Session ends and the module is unloaded when you send CTRL-C or the module decides it is done


Hello World Stap Script


probe begin
{
    print("hello world\n")
    exit()
}

Save this file as helloworld.stp. To run : stap helloworld.stp


probe begin -> Start of the system tap session
print("hello world\n") -> prints hello world
exit() -> Exits 




Comments

Post a Comment

Popular posts from this blog

bb.utils.contains yocto

-
Image
bb.utils.contains  is most commonly used function in Yocto. grep in poky directory returned with 696 count. $ grep -nr 'bb.utils.contains' poky/ | wc -l 696 It's definition is present in 'poky/bitbake/lib/bb/utils.py' file This function returns third argument if the second argument is subset of the first argument else returns fourth argument Let's take an example to understand this. You can see from the above screenshot, when the second argument is a subset of first argument, "present" was returned, else "notpresent" was returned We can also use bb.utils.contains inside if loop. This we can use inside a recipe. if ${@bb.utils.contains('SOMEFLAG','NEWVALUE3','true','false',d)}; then     FOO = 'HELLO' fi
Read more

Difference between RDEPENDS and DEPENDS in Yocto

-
We normally observe these two (RDEPENDS and DEPENDS) whenever we open any recipe. What should we choose when we write our own recipe. DEPENDS -> Build Time Dependency RDEPENDS -> Run Time Dependency DEPENDS: When a recipe 'A' is DEPENDS on recipe 'B'. In this case, Bitbake first builds recipe 'B' and then recipe 'A' E.g. You need 'dbus' to be built before 'wpa_supplicant'. RDEPENDS: When a recipe 'A' is RDEPENDS on recipe 'B'. In this case, Bitbake deploys 'B' on the target system when it deploys 'A'.  E.g. 'perf' RDEPENDS on 'bash' In other words, DEPENDS are those set of packages that should be available while building package, whereas RDEPENDS are set of packages that should be available during execution of the program.
Read more

PR, PN and PV Variable in Yocto

-
PN : Represents the name of the recipe. The name is usually extracted from the recipe file name. PR:  Represents the revision of the recipe. Default value for this revision is "r0". Subsequent revisions of the recipe conventionally will have "r1", "r2" and so on. PV:  Represents the version of the recipe. Normally extracted from the recipe file name. For example: ffmpeg_3.4.2.bb recipe. ${PN} : ffmpeg ${PV} : 3.4.2
Read more