From owner-freebsd-current Sat Dec 13 16:09:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA25788 for current-outgoing; Sat, 13 Dec 1997 16:09:22 -0800 (PST) (envelope-from owner-freebsd-current) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA25777 for ; Sat, 13 Dec 1997 16:09:14 -0800 (PST) (envelope-from grog@lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id KAA00667; Sun, 14 Dec 1997 10:39:10 +1030 (CST) (envelope-from grog) Message-ID: <19971214103908.54930@lemis.com> Date: Sun, 14 Dec 1997 10:39:08 +1030 From: Greg Lehey To: FreeBSD current users Subject: Changes in gdb -k? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I've just had a couple of panics (ffs_alloccg: map corrupted, but I think it's probably hardware), and I tried to look at them with gdb -k, but I get: #0 boot (howto=0) at ../../kern/kern_shutdown.c:285 285 dumppcb.pcb_cr3 = rcr3(); (kgdb) t Please specify a thread ID. Use the "info threads" command to see the IDs of currently known threads. (kgdb) i threads (kgdb) info threads (kgdb) t Please specify a thread ID. Use the "info threads" command to see the IDs of currently known threads. (kgdb) t 0 Thread ID 0 not known. Use the "info threads" command to see the IDs of currently known threads. (kgdb) t 1 Thread ID 1 not known. Use the "info threads" command to see the IDs of currently known threads. (kgdb) t 2 Thread ID 2 not known. Use the "info threads" command to see the IDs of currently known threads. (kgdb) q === root@freebie (/dev/ttyp4) /var/crash 9 -> wh gdb -r-xr-xr-x 1 bin bin 757760 Nov 23 18:07 /usr/bin/gdb Any ideas? Greg