From owner-freebsd-current Wed Nov 18 10:04:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA11525 for freebsd-current-outgoing; Wed, 18 Nov 1998 10:04:53 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from detlev.UUCP (tex-107.camalott.com [208.229.74.107]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA11511 for ; Wed, 18 Nov 1998 10:04:45 -0800 (PST) (envelope-from joelh@gnu.org) Received: (from joelh@localhost) by detlev.UUCP (8.9.1/8.9.1) id MAA00465; Wed, 18 Nov 1998 12:03:41 -0600 (CST) (envelope-from joelh@gnu.org) Date: Wed, 18 Nov 1998 12:03:41 -0600 (CST) Message-Id: <199811181803.MAA00465@detlev.UUCP> X-Authentication-Warning: detlev.UUCP: joelh set sender to joelh@gnu.org using -f To: freebsd-current@FreeBSD.ORG Subject: KGDB with aout From: Joel Ray Holveck Reply-to: joelh@gnu.org Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Do we have any way to do post-mortem kernel debugging of an a.out kernel, or do I need to bite the bullet and go to an ELF kernel? Are there any current caveats about an ELF kernel (or, since I haven't cvsup'd in two weeks, and we seem to be having some -current problems right now, any caveats from about 4 Nov)? Thanks, joelh -- Joel Ray Holveck - joelh@gnu.org Fourth law of programming: Anything that can go wrong wi sendmail: segmentation violation - core dumped To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message