From owner-freebsd-current Sat Oct 17 13:05:05 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA18676 for freebsd-current-outgoing; Sat, 17 Oct 1998 13:05:05 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18638 for ; Sat, 17 Oct 1998 13:04:53 -0700 (PDT) (envelope-from chuckr@mat.net) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.9.1/8.8.5) with ESMTP id QAA00404; Sat, 17 Oct 1998 16:04:13 -0400 (EDT) Date: Sat, 17 Oct 1998 16:04:13 -0400 (EDT) From: Chuck Robey To: Karl Pielorz cc: freebsd-current@FreeBSD.ORG Subject: Re: Latest kernel In-Reply-To: <3628F405.E6F17E82@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sat, 17 Oct 1998, Karl Pielorz wrote: > > OK, I set everything up. Dumpon knows where to go, savecore knows also, > > but when I actually did it, savecore told me there was no core there. > > When the kernel panics, I'm in ddb... how do I force ddb to make the > > kernel leave a core file around? > > > > I have the data, handcopied, but I want to figure from the addresses I > > have to real functions. > > Issuing 'panic' from ddb should get the system to dump the core, you should > see something like: > > " > db> panic > panic: from debugger > mp_lock = 01000002; cpuid = 1; lapic.id = 01000000 > boot() called on cpu#1 > syncing disks... 4 done Get this part, but > > dumping to dev 20009, offset 262144 > dump 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 > 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 4 5 44 43 42 41 40 39 > 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 > 12 11 10 9 8 7 6 5 4 3 2 1 0 succeeded > Automatic reboot in 15 seconds - press a key on the console to abort > Rebooting... > " I don't get this part. It's not doing the dump. I separately posted a bunch of copied-down stuff on the ddb panic info I got, but I'd sure like to see the dump, especially with the symbols from my kernel.debug (compiled from config -g). I want to know what's dying. > > (ignore the 'mp_lock and boot() called bits - I run SMP :) > > When the system reboots - you should see savecore kick in and write the dump > from the dumpdevice to /var/crash... > > Karl > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message