gdb6 and core dump

From: Matthias Schuendehuette <msch_at_snafu.de>
Date: Sat, 24 Jul 2004 23:24:53 +0200
Hi,

perhaps another annoying question, but...

to further investigate that 'dangling vnode'-Problem with vinum under 
-current  I tried to create a back trace with 'gdb kernel.debug 
vmcore.0' but all I get is:

""/disk/crash/vmcore.0" is not a core dump: File format not recognized"

whereas info.0 in /disk/crash says:

"Good dump found on device /dev/da0s1b
  Architecture: i386
  Architecture version: 1
  Dump length: 268369920B (255 MB)
  Blocksize: 512
  Dumptime: Sat Jul 10 19:40:30 2004
  Hostname:
  Versionstring: FreeBSD 5.2-CURRENT #5: Sat Jul 10 12:37:27 CEST 2004
    root_at_current.best-eng.de:/raid/obj/usr/src/sys/CURRENT
  Panicstring: unmount: dangling vnode
  Bounds: 0"

Is there something wrong with savecore(8) or is the problem (again) in 
front of the monitor?

I searched the mailing lists, looked into the developers handbook, even 
installed gdb53 from the ports but didn't have success either...


How are you creating these backtraces with gdb6?

-- 
Ciao/BSD - Matthias

Matthias Schuendehuette	<msch [at] snafu.de>, Berlin (Germany)
PGP-Key at <pgp.mit.edu> and <wwwkeys.de.pgp.net> ID: 0xDDFB0A5F
Received on Sat Jul 24 2004 - 19:24:56 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:03 UTC