From owner-freebsd-hackers Thu Oct 23 09:47:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA09632 for hackers-outgoing; Thu, 23 Oct 1997 09:47:16 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from elvis.mu.org (elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA09621 for ; Thu, 23 Oct 1997 09:47:11 -0700 (PDT) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (8.8.7/8.8.7) id LAA04258 for freebsd-hackers@freebsd.org; Thu, 23 Oct 1997 11:47:07 -0500 (CDT) (envelope-from paul) From: Paul Saab Message-Id: <199710231647.LAA04258@elvis.mu.org> Subject: Re: page fault To: freebsd-hackers@freebsd.org Date: Thu, 23 Oct 1997 11:47:07 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk J Wunsch wrote: > As Paul Saab wrote: > > > My question is without debugging > > symbols it is not possible to find out what caused the crash is > > it? > > Even without debugging symbols, the kernel usually has the default > symbol table, so you could find out in which function it happened. My > normal way of analyzation is then to recompile parts of the kernel > (the interesting parts according to the stacktrace) with -g, and have > a closer look at them. Fortunately, gcc usually produces the same > code with or without -g, provided the -O etc. flags remain the same. > > Hava a look at the section about kernel debugging in the handbook. Ok.. here is what I got... IdlePTD 21c000 current pcb at 1f16a4 panic: page fault #0 0xf0113b83 in boot () (kgdb) where #0 0xf0113b83 in boot () #1 0xf0113e42 in panic () #2 0xf01bffc6 in trap_fatal () #3 0xf01bfab4 in trap_pfault () #4 0xf01bf78f in trap () #5 0xf015a48f in tcp_ctlinput () #6 0xf01537aa in icmp_input () #7 0xf01542fe in ip_input () #8 0xf0154374 in ipintr () What does this mean? Paul