From owner-freebsd-hackers Fri Jun 20 13:14:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA22205 for hackers-outgoing; Fri, 20 Jun 1997 13:14:59 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA22193 for ; Fri, 20 Jun 1997 13:14:52 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id NAA28311; Fri, 20 Jun 1997 13:06:48 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd028307; Fri Jun 20 20:06:40 1997 Message-ID: <33AAE28B.167EB0E7@whistle.com> Date: Fri, 20 Jun 1997 13:05:31 -0700 From: Julian Elischer Organization: Whistle Communications X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386) MIME-Version: 1.0 To: Igor CC: hackers@FreeBSD.ORG Subject: Re: kernel's debugging, next References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Igor wrote: > > >>what are the methods of debugging kernel's code ? > > >trace code is one. > > Can I do on-line debugging (not post-mortem) kernel's code and how ? > Where can I read instructions ? > > --- > igor@blik.samara.su (Igor) look at http://www.freebsd.org/handbook/handbook265.html#591 this is relative and automatically generated, but it should be constant for a day or two. if it seems to be wrong just look it up in the handbook yourself.. http://www.freebsd.org/handbook