Slashdot Mirror

← Back to Stories (view on slashdot.org)

Inside the Linux kernel debugger

Posted by Hemos on from the don't-violate-SCO dept.

An anonymous reader writes "Here's a good article that shows you how to install and set up the kernel debugger (KDB) to trace Linux kernel execution and examine memory and data structures. The best part is, you don't need a separate machine for debugging."

4 of 28 comments (clear)

  1. Beos was better. by Anonymous Coward · · Score: 2, Interesting

    BeOS had a nifty debugger that you dropped into instead of BSOD. you could do all sorts of fun things, and it even allowed modules to be loaded to add new debug commands.

  2. Visual debuggers by ObviousGuy · · Score: 4, Interesting

    I have no doubt that KDB is a powerful debugger, but having a GUI would make it even better, IMO.

    This probably comes from my own experience with OS debuggers and Application debuggers (windbg, VC++/Borland C++). Being able to get immediate feedback about program state without having to enter arcane commands is a definite boon.

    Are there any GUI wrappers available for KDB?

    --
    I have been pwned because my /. password was too easy to guess.
    1. Re:Visual debuggers by weicco · · Score: 2, Interesting

      SoftIce ported on Linux/Unix would be grrrreat. I refused to write any driver code until I got myself a SoftIce in dev-computer at my last job :) Unfortunately SoftIce costs more than family wagon I think.

      --
      You don't know what you don't know.
  3. Much easier to use User-Mode Linux by Ristretto · · Score: 2, Interesting

    We're doing OS research here (UMass) with Linux, and unless you have very specialized needs, you're far better off using User-Mode Linux. By running Linux as a user-process, you don't have to worry about bringing down your machine and you can use gdb to do your debugging.