From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6993 invoked by alias); 3 Dec 2005 03:33:40 -0000 Received: (qmail 6826 invoked by uid 22791); 3 Dec 2005 03:33:39 -0000 X-Spam-Check-By: sourceware.org Received: from nevyn.them.org (HELO nevyn.them.org) (66.93.172.17) by sourceware.org (qpsmtpd/0.31.1) with ESMTP; Sat, 03 Dec 2005 03:33:38 +0000 Received: from drow by nevyn.them.org with local (Exim 4.54) id 1EiO9Y-00068j-Eu; Fri, 02 Dec 2005 22:33:36 -0500 Date: Sat, 03 Dec 2005 03:33:00 -0000 From: Daniel Jacobowitz To: Russell Shaw Cc: gdb@sourceware.org Subject: Re: [RFC] plugin/extension interface Message-ID: <20051203033336.GA23537@nevyn.them.org> Mail-Followup-To: Russell Shaw , gdb@sourceware.org References: <200512021936.jB2JaZ6n014666@elgar.sibelius.xs4all.nl> <8f2776cb0512021412n17d2a8b2rf8cb4a48daa9449e@mail.gmail.com> <200512022241.jB2Mf3Fk024314@elgar.sibelius.xs4all.nl> <8f2776cb0512021507m52b9d491gd4ddc0ceaab594ba@mail.gmail.com> <20051202233207.GA19812@nevyn.them.org> <8f2776cb0512021657i3f780f77sb1294b51753ffaaa@mail.gmail.com> <20051203023154.GA22527@nevyn.them.org> <439105DF.5040708@netspace.net.au> <20051203024500.GA22826@nevyn.them.org> <43910D47.2070300@netspace.net.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <43910D47.2070300@netspace.net.au> User-Agent: Mutt/1.5.8i X-IsSubscribed: yes Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2005-12/txt/msg00022.txt.bz2 On Sat, Dec 03, 2005 at 02:13:11PM +1100, Russell Shaw wrote: > The way gdb works, when i type: target avrjtagice -d /dev/ttyS2, > gdb uses (or registers) using: void _initialize_remote_jtag (void). Incorrect; that happens at GDB startup. > If the functions (or framework) used in these target interfaces are > documented, the problems would be solved with little other than a bit > of documentation work. Not unless we declared them a public interface. That means supporting them, preserving compatibility, et cetera. We are not prepared to do that. > I couldn't use the default target protocol, because i wasn't interfacing > to an end target. I was interfacing to an ICE debugger (that already had > its own protocol) for the target. > > I did it to replace the current hack of having an extra program on the > pc that converts between the default gdb target protocol, and this ICE- > specific protocol. > > The conversion hack was extremely slow, clumsy, fault-intolerant, and > error-prone. I would need to know a lot more about these problems, but it is very likely that they are problems with the conversion program - not with the concept. If they were problems with the remote protocol, we would be interested in fixing them. -- Daniel Jacobowitz CodeSourcery, LLC