From owner-freebsd-hackers Wed May 24 18: 9:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from bubba.whistle.com (bubba.whistle.com [207.76.205.7]) by hub.freebsd.org (Postfix) with ESMTP id 2BF6F37BAA5 for ; Wed, 24 May 2000 18:09:55 -0700 (PDT) (envelope-from archie@whistle.com) Received: (from archie@localhost) by bubba.whistle.com (8.9.3/8.9.2) id SAA02960; Wed, 24 May 2000 18:07:59 -0700 (PDT) From: Archie Cobbs Message-Id: <200005250107.SAA02960@bubba.whistle.com> Subject: Re: boot/kernel debugging In-Reply-To: from Nick Hibma at "May 21, 2000 12:02:53 pm" To: n_hibma@calcaphon.com (Nick Hibma) Date: Wed, 24 May 2000 18:07:59 -0700 (PDT) Cc: jcm@freebsd-uk.eu.org (J McKitrick), hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Nick Hibma writes: > In general it is well possible to single step anything in the > kernel. You might find occasions where things stop working, and odd > cases were things all of a sudden start working, but normally, apart > from hardware things, most things are not time critical, or create > problems through spin locks. > > You can single step at boot time, by setting the flags in the loader. > > set boot_ddb # jump to debugger > set boot_gdb # use remote gdb for debugging by default Also don't for get 'sysctl -w debug.enter_debugger=ddb' (or gdb) to enter the debugger from the command line. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message