From owner-freebsd-hackers Wed May 17 20:52:30 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from probity.mcc.ac.uk (probity.mcc.ac.uk [130.88.200.94]) by hub.freebsd.org (Postfix) with ESMTP id CC27C37B703 for ; Wed, 17 May 2000 20:52:20 -0700 (PDT) (envelope-from jcm@freebsd-uk.eu.org) Received: from dogma.freebsd-uk.eu.org ([130.88.200.97]) by probity.mcc.ac.uk with esmtp (Exim 1.92 #3) for hackers@freebsd.org id 12sHMB-0007mr-00; Thu, 18 May 2000 04:52:19 +0100 Received: (from jcm@localhost) by dogma.freebsd-uk.eu.org (8.9.3/8.9.3) id EAA59943 for hackers@freebsd.org; Thu, 18 May 2000 04:52:19 +0100 (BST) (envelope-from jcm) Date: Thu, 18 May 2000 04:52:19 +0100 From: J McKitrick To: hackers@freebsd.org Subject: boot/kernel debugging Message-ID: <20000518045219.A59839@dogma.freebsd-uk.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I've used softice for debugging under windows, and i was wondering if gdb offers similar capabilities. It seems the best way to debug the ECP parallel port problem is to step through the code during the boot phase. Can this be done, or is there too much timing-critical stuff going on then? jm -- ------------------------------------------------------------------- Jonathon McKitrick -- jcm@freebsd-uk.eu.org I am a bomb technician. If you see me running, try to keep up. ------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message