Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 24 Nov 2003 13:42:46 +1030
From:      Greg 'groggy' Lehey <grog@FreeBSD.org>
To:        Kent Kuriyama <kuriyama@newhost.cpf.navy.mil>
Cc:        questions@freebsd.org
Subject:   Re: Questions regarding use of 'gdb -k'
Message-ID:  <20031124031246.GW82843@wantadilla.lemis.com>
In-Reply-To: <200311240302.hAO329T5041876@newhost.cpf.navy.mil>
References:  <200311240302.hAO329T5041876@newhost.cpf.navy.mil>

next in thread | previous in thread | raw e-mail | index | archive | help

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031124031246.GW82843>