From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12014 invoked by alias); 24 Jun 2014 13:56:57 -0000 Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org Received: (qmail 11999 invoked by uid 89); 24 Jun 2014 13:56:55 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.5 required=5.0 tests=AWL,BAYES_50,RCVD_IN_BRBL_LASTEXT,T_RP_MATCHES_RCVD autolearn=no version=3.3.2 X-HELO: satelite.dea.inpe.br Received: from satelite.dea.inpe.br (HELO satelite.dea.inpe.br) (150.163.30.1) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-SHA encrypted) ESMTPS; Tue, 24 Jun 2014 13:56:53 +0000 Received: from FabricioHP (fabricio.dea.inpe.br [150.163.30.16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: fabricio) by satelite.dea.inpe.br (Postfix) with ESMTPSA id DA219E01AA; Tue, 24 Jun 2014 11:17:05 -0300 (BRT) From: =?UTF-8?Q?Fabr=C3=ADcio_de_Novaes_Kucinskis?= To: "'Breazeal, Don'" , References: <20140621011016.M65772@satelite.dea.inpe.br> <53A4DB40.2040103@codesourcery.com> <002301cf8ef2$6af896e0$40e9c4a0$@dea.inpe.br> <53A84B9C.4000204@codesourcery.com> In-Reply-To: <53A84B9C.4000204@codesourcery.com> Subject: RES: RES: How to update an old GDBServer to implement gdb/mi? Date: Tue, 24 Jun 2014 13:56:00 -0000 Message-ID: <005101cf8fb3$f6fa4af0$e4eee0d0$@dea.inpe.br> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-IsSubscribed: yes X-SW-Source: 2014-06/txt/msg00074.txt.bz2 Hello Don, Thanks very much for the clarification. I'm studying the links you've sent = and some more, and it really seems that it' s a matter of configuration (an= d maybe one or two commands absent from our GDBServer implementation...). Regards, Fabr=C3=ADcio. -----Mensagem original----- De: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] Em nome de B= reazeal, Don Enviada em: segunda-feira, 23 de junho de 2014 12:46 Para: Fabr=C3=ADcio de Novaes Kucinskis; gdb@sourceware.org Assunto: Re: RES: How to update an old GDBServer to implement gdb/mi? On 6/23/2014 7:50 AM, Fabr=C3=ADcio de Novaes Kucinskis wrote: > Hello Yao, and thanks for your answer. > > I'm not sure if I was clear enough, so I add some more detail: my GDB Ser= ver runs on a board with SPARC processor (more specifically, an ERC32), and= is installed just after the boot loader and the start of the C runtime. Th= ere's no operating system under the GDB Server. > > On the gdb "host" side, I already use a GDB built for the sparc target, w= hich works pretty well when debugging by command line or using an old front= -end like DDD. But not with Eclipse or any modern front-end - and I assumed= this would be due to the lack of support for the MI protocol by my GDBServ= er. > > So, are you saying that the gdb executable should be translating the "MI"= commands received by Eclipse CDT and sending them as CLI commands to my bo= ard? Who has to "speak" MI? The GDBServer on my board or the gdb executable= built for sparc target? > > Thanks again for your attention, > > Fabr=C3=ADcio. Fabricio, MI is used for communication between Eclipse (or other tools) and GDB. It is not used for communication with GDBserver, RSP is used for that. The block diagram looks something like this: Eclipse <=3D=3D MI =3D=3D> GDB <=3D=3D RSP =3D=3D> GDBserver MI support should already be built in to your GDB executable, you can try i= t using the --interpreter option. See https://sourceware.org/gdb/onlinedocs/gdb.html#Mode-Options and https://sourceware.org/gdb/onlinedocs/gdb.html#GDB_002fMI It seems to me that all the pieces that you need probably already exist in = some form, it is just a matter of putting them together to do what you want. --Don > > > -----Mensagem original----- > De: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] Em nome > de Yao Qi Enviada em: sexta-feira, 20 de junho de 2014 22:09 > Para: Fabricio de Novaes Kucinskis; gdb@sourceware.org > Assunto: Re: How to update an old GDBServer to implement gdb/mi? > > On 06/21/2014 09:12 AM, Fabricio de Novaes Kucinskis wrote: >> I have a SPARC V7 processor with an old GDB Server implemented for >> cross- debugging. In order to debug my software with a modern >> front-end such as the Eclipse CDT, I have to update this server to use t= he MI interface. >> >> I know reasonably well my old GDB Server implementation, but I have >> no idea what changes I have to apply in order to support the MI interfac= e. >> >> So I'd like to ask: from were should I start? Can someone send me >> usefull tips or links for this task? > > GDBserver doesn't support MI but GDB does. You can configure and build g= db for sparc target, use this gdb in Eclipse CDT, and connect to your old G= DBserver. > > -- > Yao (=E9=BD=90=E5=B0=A7) > > > --- > Este email est=C3=A1 limpo de v=C3=ADrus e malwares porque a prote=C3=A7= =C3=A3o do avast! Antiv=C3=ADrus est=C3=A1 ativa. > http://www.avast.com > --- Este email est=C3=A1 limpo de v=C3=ADrus e malwares porque a prote=C3=A7=C3= =A3o do avast! Antiv=C3=ADrus est=C3=A1 ativa. http://www.avast.com