Linux kernel debugging going beyond printk messages - Sergio Prado

YouTube Excerpt: Debugging the Linux kernel with printk messages is a common technique. And often a good one. The problem happens when we only know this debugging technique. How to debug a kernel oops message? How to trace and understand the kernel execution? How to identify and analyze a buffer overflow? How to identify a memory leak or a deadlock in kernel space? In many situations, there are more effective kernel debugging tools and techniques, including KGDB, ftrace, addr2line, kmemleak, and so on. In this presentation, we will go over these and many other very useful tools to identify and fix problems in the Linux kernel. FULL DESCRIPTION AND SLIDES: https://cfp.linuxdev-br.net/2019/talk/F7PJJU/ BIO: Sergio Prado has been working with embedded systems for more than 20 years. He is active in the embedded systems community in Brazil, maintaining some mailing lists and writing in his personal blog sergioprado.org. He is an entrepreneur, founder of Embedded Labworks and Linux developer, contributing to several free software projects, including Buildroot, Yocto Project and the Linux kernel. THE CONFERENCE: Linux Developer Conference Brazil aims to take the Brazilian Linux development community to the international level. Whether you are just curious and want to understand the Linux ecosystem, someone seeking to contribute to FOSS projects, or even a seasoned collaborator, this conference is for you. Site: https://linuxdev-br.net/ Follow us on Twitter: https://twitter.com/linuxdevbr

Debugging the Linux kernel with printk messages is a common technique. And often a good one. The problem happens when we only know this debugging...

Read Full Article 🔍

Curious about Linux Kernel Debugging Going Beyond Printk Messages - Sergio Prado's Color? Explore detailed estimates, income sources, and financial insights that reveal the full picture of their profile.

Source ID: tW3BKNsJoy8

Category: color style guide