From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 14 03:46:32 2005 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7E18F16A4CE for ; Mon, 14 Feb 2005 03:46:32 +0000 (GMT) Received: from duchess.speedfactory.net (duchess.speedfactory.net [66.23.201.84]) by mx1.FreeBSD.org (Postfix) with SMTP id EDFC643D45 for ; Mon, 14 Feb 2005 03:46:31 +0000 (GMT) (envelope-from ups@tree.com) Received: (qmail 2203 invoked by uid 89); 14 Feb 2005 03:46:31 -0000 Received: from duchess.speedfactory.net (66.23.201.84) by duchess.speedfactory.net with SMTP; 14 Feb 2005 03:46:31 -0000 Received: (qmail 2188 invoked by uid 89); 14 Feb 2005 03:46:31 -0000 Received: from unknown (HELO palm.tree.com) (66.23.216.49) by duchess.speedfactory.net with SMTP; 14 Feb 2005 03:46:31 -0000 Received: from [127.0.0.1] (localhost.tree.com [127.0.0.1]) by palm.tree.com (8.12.10/8.12.10) with ESMTP id j1E3kTw6045364; Sun, 13 Feb 2005 22:46:30 -0500 (EST) (envelope-from ups@tree.com) From: Stephan Uphoff To: Gerald Heinig In-Reply-To: <420B938D.2040708@syskonnect.de> References: <420731DD.3050206@syskonnect.de> <42088232.1030001@syskonnect.de> <1107888844.6309.221.camel@palm.tree.com> <1107964038.6309.1137.camel@palm.tree.com> <420B938D.2040708@syskonnect.de> Content-Type: text/plain Message-Id: <1108352789.6309.9948.camel@palm.tree.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Sun, 13 Feb 2005 22:46:29 -0500 Content-Transfer-Encoding: 7bit cc: hackers@freebsd.org Subject: Re: Firewire blues X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 14 Feb 2005 03:46:32 -0000 On Thu, 2005-02-10 at 12:02, Gerald Heinig wrote: > Stephan Uphoff wrote: > > Once I linked in dcons, dcons_crom and firewire into the kernel > > everything worked. (I think only dcons is really needed - maybe a link > > set issue?) > > I only used the gdb stub method. > > > > Can you send me your dmesg? (After you linked the dcons stuff into the > > kernel) > > Another thing: what system are you on? -current? > I'm using 5.3-RELEASE and I've noticed that a lot of the commands and > responses in the HowTo are different to my system. > Could that be the problem? > > Cheers, > Gerald OK - I finally managed to try this on a newly installed 5.3-RELEASE. I copied the GENERIC config file (to GENERIC.debug) and added a few lines diff -u GENERIC GENERIC.debug --- GENERIC Sun Oct 24 14:02:52 2004 +++ GENERIC.debug Mon Feb 14 03:15:21 2005 @@ -24,6 +24,14 @@ cpu I686_CPU ident GENERIC +makeoptions DEBUG=-g # Build kernel with gdb(1) debug symbols +options KDB # Enable kernel debugger support. +options DDB # Support DDB. +options GDB # Support remote GDB. +options ALT_BREAK_TO_DEBUGGER +device dcons +device dcons_crom + # To statically compile in device wiring instead of /boot/device.hints #hints "GENERIC.hints" # Default places to look for devices. Then configured/compiled/installed the GENERIC.debug kernel. Copied the kernel.debug file in the GENERIC.debug compile directory to the debug station and rebooted the target machine. After reboot I set the default debugger to gdb target# sysctl -w debug.kdb.current=gdb and entered the debugger target# sysctl -w debug.kdb.enter=1 On the debugging station I entered debug 1# dconschat -br -G 5555 -t and then in another window debug 2# kgdb -r :5555 kernel.debug And it just worked for me. I have to admit that my debugging machine is not 5.3 .. but I believe I used the same setup with pre 5.3 userland before. Let me know if you can repeat my steps. If not then I can set up a 5.3 debugging station in the next days. Stephan