Greg,
Thanks. Regarding the suspected corrupt dump file. In the syslog I can
see the dump file being created (actually 'vmcore') and there are no
error messages. Are you saying that the corruption occurs during
the writing of the file or is the data resident in memory corrupt?
I suspect that something is wrong with the hardware on this
box. We moved the hard drive from one motherboard to another but the
problem remains. This leaves the hard drive as suspect but there are
no syslog messages to indicate a drive problem. The system is running
4.8 p13. Thanks.
Kent
>
>
> --vS2hnRoLMmJ4tslQ
> Content-Type: text/plain; charset=us-ascii
> Content-Disposition: inline
>
> On Sunday, 23 November 2003 at 17:02:09 -1000, Kent Kuriyama wrote:
> > I am having difficulty in using 'gdb -k' to track down a kernel panic. I
> > have built a version of the kernel with the debugging symbols. After
> > the crash I use the 'gdb -k' command but get the following output:
> >
> > --
> > chinmon1# gdb -k /data1/src/sys/compile/ata/kernel.debug /var/crash/kernel.29
> > GNU gdb 4.18 (FreeBSD)
> > 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 "i386-unknown-freebsd"...Deprecated bfd_read called a
> > t /data1/src/gnu/usr.bin/binutils/gdb/../../../../contrib/gdb/gdb/dbxread.c line
> > 2627 in elfstab_build_psymtabs
> > Deprecated bfd_read called at /data1/src/gnu/usr.bin/binutils/gdb/../../../../co
> > ntrib/gdb/gdb/dbxread.c line 933 in fill_symbuf
> >
> > IdlePTD at phsyical address 0x
> > initial pcb at physical address 0x0048cee0
> >
> > cannot read proc at 0
> > (kgdb) where
> > #0 0x0 in ?? ()
> > (kgdb) exit
> > Undefined command: "exit". Try "help".
> > (kgdb) chinmon1#
> > --
> >
> > Can you tell me what I am doing wrong? Thanks.
>
> Unfortunately, this looks like you have a corrupted dump. What you've
> done (with the exception of "exit") is correct. You might find it
> better to use serial debugging if this is repeatable.
>
> Greg
> --
> When replying to this message, please copy the original recipients.
> If you don't, I may ignore the reply or reply to the original recipients.
> For more information, see http://www.lemis.com/questions.html
> See complete headers for address and phone numbers.
>
> --vS2hnRoLMmJ4tslQ
> Content-Type: application/pgp-signature
> Content-Disposition: inline
>
> -BEGIN PGP SIGNATURE-
> Version: GnuPG v1.2.0 (FreeBSD)
>
> iD8DBQE/wXcuIubykFB6QiMRAkNFAKCUw+vNGXhkmldkMiHKLtEozIv0mgCfanmY
> aLywfIVWTuCH0Ub9op8+Z6I=
> =Y7dr
> -END PGP SIGNATURE-
>
> --vS2hnRoLMmJ4tslQ--
>
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
