Here's the result of the dmesg and gdb session:

hw-sbus# dmesg -M netbsd.0.core
dmesg: magic number incorrect
hw-sbus# gdb netbsd.0
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "sparc--netbsd"...(no debugging symbols found)...
(gdb) target kcore netbsd.0.core
panic: ffs_valloc: dup alloc
#0  0xf002d7b8 in mi_switch ()
(gdb) where
#0  0xf002d7b8 in mi_switch ()
#1  0xf002d128 in tsleep ()
#2  0xf00df780 in uvm_scheduler ()
#3  0xf001d914 in main ()
(gdb) q
hw-sbus# uname -a
NetBSD hw-sbus 1.4.2 NetBSD 1.4.2 (HWSBUS) #0: Thu Jan 25 16:08:11 EST 2001
    root@hw-sbus:/usr/src/sys/arch/sparc/compile/HWSBUS sparc
hw-sbus# ls -l
total 66432
-rw-------  1 root  wheel   1526119 Jan 30 15:15 netbsd.0
-rw-------  1 root  wheel  66441752 Jan 30 15:15 netbsd.0.core
hw-sbus# pwd
/usr/export/home/root_temp
hw-sbus# 

I had to move the dump off of /var since my root partition was filling up.



At 11:34 PM 1/30/01 +0100, Manuel Bouyer wrote:
>On Tue, Jan 30, 2001 at 03:39:40PM -0500, Steven Grunza wrote:
>> After running GENERIC for over 100 days, I built my own kernel.  After some
>> hours or days, it crashed and created a core in /var/crash
>> 
>> What's the best way to figure out why it crashed?  I don't have a serial
>> console on this machine most of the time and it doesn't have a display
>> monitor.
>
>'dmesg -M /var/crash/netbsd.0.core'
>And to analyse the dump with gdb:
>gdb /var/crash/netbsd.0
>target kcore /var/crash/netbsd.0.core
>
>--
>Manuel Bouyer <bouyer@antioche.eu.org>
>--
>
>