From owner-freebsd-hackers Fri Aug 30 09:50:14 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA04761 for hackers-outgoing; Fri, 30 Aug 1996 09:50:14 -0700 (PDT) Received: from precipice.shockwave.com (ppp-206-170-5-18.rdcy01.pacbell.net [206.170.5.18]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id JAA04756 for ; Fri, 30 Aug 1996 09:50:11 -0700 (PDT) Received: from shockwave.com (localhost.shockwave.com [127.0.0.1]) by precipice.shockwave.com (8.7.5/8.7.3) with ESMTP id JAA06010; Fri, 30 Aug 1996 09:49:22 -0700 (PDT) Message-Id: <199608301649.JAA06010@precipice.shockwave.com> To: Bruce Evans cc: julian@whistle.com, hackers@FreeBSD.org Subject: Re: gdb remote In-reply-to: Your message of "Sat, 31 Aug 1996 00:56:56 +1000." <199608301456.AAA07864@godzilla.zeta.org.au> Date: Fri, 30 Aug 1996 09:49:22 -0700 From: Paul Traina Sender: owner-hackers@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk The current way the SIO is handled for the console is utterly gross. This was one of the things I was hoping someone else would get a chance to fix. :-( The boot flags work as follows: -d = stop in debugger debugger (gdb or ddb) at boot -g = debugger should talk GDB protocol ddb also has a new "gdb" command to toggle between ddb and gdb on the next exception So, if I forget to do anything special, I can ctl-alt-esc (if vty), break (if serial) to DDB on the system console, type gdb, continue, and break again. Paul p.s. if someone want's to work on serial console code, please DO.