* Greg Lehey ([EMAIL PROTECTED]) [990731 03:50]:
> On Saturday, 31 July 1999 at  0:19:27 +0200, Jeroen Ruigrok/Asmodai wrote:
> > * Greg Lehey ([EMAIL PROTECTED]) [990730 11:23]:
> >> On Friday, 30 July 1999 at  8:45:32 +0200, Jeroen Ruigrok/Asmodai wrote:

> >> 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:
> >
> > (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 ?? ()
> 
> Hmm, that doesn't look like a dump from ddb.  Did you have
> DDB_UNATTENDED set?

No, just options DDB.
This bt was obtained after doing gdb -k kernel.0 vmcore.0
I still have the DDB trace on paper which I can type in if needed/wanted.

> What you do with the results depends a lot on what you find.  On the
> whole, I wouldn't think it worth the pain of debugging without
> symbols.

No it isn't...
I just made world and am building two kernels now (one with and one
without debug info) so that the next time something happens like that
I am prepared.

Thanks anyways for the help Greg, this will surely help some parts of
the PDP, hope I get some stuff in there about this sort of thing today.

'gards,

-- 
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

Reply via email to