From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 331 invoked by alias); 24 Jan 2004 00:55:23 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 323 invoked from network); 24 Jan 2004 00:55:22 -0000 Received: from unknown (HELO home.ringle.org) (12.153.69.6) by sources.redhat.com with SMTP; 24 Jan 2004 00:55:22 -0000 Received: by home.ringle.org (Postfix, from userid 501) id 981F7B7F3D; Fri, 23 Jan 2004 19:55:12 -0500 (EST) From: Jon Ringle To: gdb@sources.redhat.com Subject: Re: minimal stub? (GDB Remote Serial Protocol) Date: Sat, 24 Jan 2004 00:55:00 -0000 User-Agent: KMail/1.5 References: In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200401231955.12261.jon.ringle@comdial.com> X-SW-Source: 2004-01/txt/msg00283.txt.bz2 On Friday 23 January 2004 06:06 pm, Vijay Kamarshi wrote: > Hi all, > > I am planning on using GDB to debug a remote processor running a debug > stub. It is quite concerning to me that the remote protocol document is > out-of-date. Is it that easy to figure out what the protocol is by > experimentation? For example if the GDB host sends a stream of commands to > the remote processor and it mis-interprets the first one, is the host not > going to just quit on that? That would make the experimentation process > pretty long! > > I am puzzled: > 1) are there no people out there who have this protocol figured out? I > would appreciate at least a starting point! > 2) are all the commands in the remote protocol document out of date or just > some of them? > > Any help would be gratefully received. > > -Vijay Kamarshi > PS: I heard that one way of figuring out this remote protocol is to peer > deeply into gdbserver, but people have warned me that it is a pretty hairy > piece of code. Hi Vijay, A while back I backported an arm kgdb patch for kernel 2.4.19 to a target based on kernel 2.2.16 found at: http://www.arm.linux.org.uk/developer/patches/viewpatch.php?id=1335/1 It may be helpful. Jon