Linux-kernel mailing list archive 1998-48,: Re: kernel debugging

# Re: kernel debugging

christophe.leroy5@capway.com
Wed, 2 Dec 1998 16:24:55 +0100

- Messages sorted by: [ date ][ thread ][ subject ][ author ]
- Next message: Stephen C. Tweedie: "Re: NTP dumps Linux, film at 11. [Fwd/FYI]"
- Previous message: Stephen C. Tweedie: "Re: 2.1.130 kernel Oops"
- Maybe in reply to: Jason Casmira: "kernel debugging"

From: owner-linux-kernel-digest@vger.rutgers.edu
To: linux-kernel-digest@vger.rutgers.edu
Subject: linux-kernel-digest V1 #2925
Send reply to: linux-kernel@vger.rutgers.edu
Date sent: Wed, 2 Dec 1998 04:19:11 -0500

> From: Jason Casmira <cazman@indra.com>
> Date: Tue, 01 Dec 1998 20:35:58 -0700
> Subject: kernel debugging
>
> I have performed this type of work before, but never with
> available source code. Therefore, I was wondering if anyone
> could suggest some resources for performing kernel debugging
> & tracing.
>
>
> Since subscribing to this list, I've seen lots of patches, mods,
> etc., and am wondering how these are being tested & debugged.
>

I think most of us are using printk() inside kernel source to view
what we want.

You can also compile kernel with -g (without removing -O2), then
analyse kernel memory as a core file by doing

gdb /usr/src/linux/vmlinux /proc/kcore

christophe leroy

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

- Next message: Stephen C. Tweedie: "Re: NTP dumps Linux, film at 11. [Fwd/FYI]"
- Previous message: Stephen C. Tweedie: "Re: 2.1.130 kernel Oops"
- Maybe in reply to: Jason Casmira: "kernel debugging"