Debugging Linux Kernel using KGDB Part8 - Debugging Kernel Module

-
In this post, we will debug the e1000 module present on our Ubuntu VM.

Steps for debugging using KGDB:

On the target:
gdb client needs to know the load address of the kernel module
$ cat /sys/module/e1000/sections/.text
0xffffffffc0091000

Switch to KGDB Debugger mode by activating magic sysrq
$ echo 'ttyS1,115200' > /sys/module/kgdboc/parameters/kgdboc
$ echo g > /proc/sysrq-trigger

On the Development Machine:
Run the following commands:
$ gdb ./vmlinux
$ target remote /dev/ttyS1
$ add-symbol-file drivers/net/ethernet/intel/e1000/e1000.ko  0xffffffffc0091000


Let's put breakpoint at e1000_xmit_frame which is called while transmitting a frame.

(gdb) break e1000_xmit_frame
Breakpoint 1 at 0xffffffffc0092f90: file drivers/net/ethernet/intel/e1000/e1000_main.c, line 3102.
(gdb) c

Now see as soon as it transmits a packet, system will stop and enter into kgdb session






Comments

  1. Nina Athena27 February 2020 at 10:42

    Thank you for sharing this! What you have shared is very helpful and informative. Would love to see more updates from you.

    Website Development

    ReplyDelete
  2. amit2 August 2022 at 10:55

    The tutorials are very helpful,thanks.
    I tried the same steps as mentioned in tutorial but facing some issues.
    When i insmod the kernel module on target(Beagle-Bone),i don't see a .text section under /sys/module//sections/.
    Any input on this will be helpful.

    ReplyDelete
    Replies
    1. Dmitry Klionsky30 November 2023 at 03:58

      The below command also gives the module's loaded address

      ```
      $ sudo grep MODULE_NAME /proc/modules
      ```

      Delete

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