From owner-freebsd-hackers Wed Mar 27 03:36:04 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id DAA21550 for hackers-outgoing; Wed, 27 Mar 1996 03:36:04 -0800 (PST) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id DAA21495 for ; Wed, 27 Mar 1996 03:36:01 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id DAA04484; Wed, 27 Mar 1996 03:35:47 -0800 (PST) To: Barry Perryman cc: hackers@freebsd.org Subject: Re: Ok, I'll bite... In-reply-to: Your message of "Wed, 27 Mar 1996 09:37:50 GMT." Date: Wed, 27 Mar 1996 03:35:47 -0800 Message-ID: <4482.827926547@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Just what is this gdb-remote that Jordan keeps mentioning in an almost > subliminal way ? I'm not sure what [gdb-remote!] you mean by this but [gdb-remote!] I'll do by best to answer your question. Basically, it's a protocol that gdb can speak with a remote process (be it a kernel or whatever) to control it. It's basically just a stream of text that the remote end emits in answer to various gdb queries. Imagine for a moment using ddb as an interactive user, deciding that you don't _quite_ like the interface it provides and then writing a program which will spit out ddb commands on your behalf and digesting and reformatting the results that ddb prints back. gdb-remote allows you to do your debugging from gdb using a different box and with the complete sources (from which, presumably, the kernel was built) local to that box for source-level debugging. Jordan [gdb-remote!]