linux-kernel - linux kernel debugging

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <1e15d0630806042321l4fca3c17m3660ba3da517dbc3@mail.gmail.com>
Date:	Wed, 4 Jun 2008 23:21:45 -0700
From:	"Stéphane Charette" <stephanecharette@...il.com>
To:	linux-kernel@...r.kernel.org
Subject: linux kernel debugging

Back in the 2.2.13 kernel days, I would hook up 2 computers via serial
ports and could use ddd/gdb to walk through the kernel on the 2nd
computer.

My old notes tells me I would enabled "Kernel Hacking -> Kernel
support for GDB" when running "make menuconfig", and then add "gdb
gdbttyS=1 gdbbaud=115200" when booting the 2nd computer.

Is this still the way to do it?

I'd like to play around with this again after many years of not having
looked at the kernel internals.  One of the things I found tonight
while searching for info on the web is this:

http://kgdb.linsyssoft.com

Is this what it has evolved into, or is this something else?  It looks
like a commercial product, which is why I was reluctant to dig further
into it.  I guess what I'm asking is:  What is the most common method
people use to walk a debugger through the linux kernel?

Thanks,

Stéphane Charette
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/