* Greg Lehey ([EMAIL PROTECTED]) [990730 11:23]:
> On Friday, 30 July 1999 at 8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote:
> > I started a make world on my box last night and then proceeded to go to bed.
> >
> > When I looked at my console this morning it had sprung into DDB because
> > of a panic: ffs_alloccg: map corrupted.
>
> The first question is: do you have a kernel with debug symbols? If
> not, gdb isn't going to help you much. bde can do it with ddb (though
> it's a bit late if you have the dump), but mere mortals are in trouble
> without symbols.
I thought I had one, but alas I didn't. *sigh* One of those days when ye
bump against stuff you should've done. Learned from that in a multiple
ways, so next time I got everything I need...
> The first thing you should do with any dump is a backtrace (bt). The
> appearance depends on how you got there. Since you appear to have
> gone via ddb, your dump should look something like this:
Here is at least some info:
(kgdb) bt
#0 0xc0155f14 in boot ()
#1 0xc0156249 in panic ()
#2 0xc01e737b in ffs_mapsearch ()
#3 0xc01e5cea in ffs_alloccg ()
#4 0xc01e5756 in ffs_hashalloc ()
#5 0xc01e4adc in ffs_alloc ()
#6 0xc01e7af0 in ffs_balloc ()
#7 0xc01f0a5c in ffs_write ()
#8 0xc01827ce in vn_write ()
#9 0xc01623ac in dofilewrite ()
#10 0xc01622bb in write ()
#11 0xc0225066 in syscall ()
#12 0xc02192b6 in Xint0x80_syscall ()
#13 0x807d24a in ?? ()
#14 0x807666d in ?? ()
Think I'll read up on GDB in my printed manual...
Other hints/tips still welcome, I still have the dumps =)
--
Jeroen Ruigrok van der Werven asmodai(at)wxs.nl
The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>
Network/Security Specialist BSD: Technical excellence at its best
Cum angelis et pueris, fideles inveniamur. Quis est iste Rex gloriae...?
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
