Debugging technology of embedded Linux reading notes

For complex Linux drivers and libraries such as HAL, you need to debug them using a variety of methods. For example, set breakpoints, step-tracking code, output debug values, and so on. Although there is no visual Studio, Delphi, Eclipse in the debugging aspect of the vision of the work, but to learn some of this technology is undoubtedly even more strange feet hand bright strong and stable Linux kernel modules for embedded Linux core modules, can be FA, It may be more complicated to debug the Chengzhuang and central repository. Because you need at least two machine development machines and target machines when you lose a lot of praise.

In Linux file systems,/proc is often used as a tool for data intersection =ee of kernel space and user space. The/proc file system behaves like a device file system C/dev). /proc is a virtual file system, which means that/proc is not a real file system, but a memory map. All read-write/PROC_ operations are read and write to memory, so reading and writing/proc file systems is much faster than reading/writing/dev file systems. As a result, the/proc file system can also serve as a tool for Linux to interact with user-space programs.

Linux kernel debugging has been considered by many people to be very difficult. , most people prefer to use the PRINTK function directly to output debug information, and are reluctant to use various commands-(GDB, Gdbserv~r,. KGDB, etc.) to debug. , because it's not going to change. More benefits. In addition to the traditional PRINTK function debugging technology, this chapter also introduces other debugging techniques. , these debugging techniques do not necessarily need to be used.

Debugging technology of embedded Linux reading notes