From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9538 invoked by alias); 23 Jun 2014 14:51:31 -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 9448 invoked by uid 89); 23 Jun 2014 14:51:30 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=1.4 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; Mon, 23 Jun 2014 14:51:24 +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 64F59E016E for ; Mon, 23 Jun 2014 12:11:40 -0300 (BRT) From: =?UTF-8?Q?Fabr=C3=ADcio_de_Novaes_Kucinskis?= To: References: <20140621011016.M65772@satelite.dea.inpe.br> <53A4DB40.2040103@codesourcery.com> In-Reply-To: <53A4DB40.2040103@codesourcery.com> Subject: RES: How to update an old GDBServer to implement gdb/mi? Date: Mon, 23 Jun 2014 14:51:00 -0000 Message-ID: <002301cf8ef2$6af896e0$40e9c4a0$@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/msg00069.txt.bz2 Hello Yao, and thanks for your answer. I'm not sure if I was clear enough, so I add some more detail: my GDB Serve= r runs on a board with SPARC processor (more specifically, an ERC32), and i= s installed just after the boot loader and the start of the C runtime. Ther= e's no operating system under the GDB Server. On the gdb "host" side, I already use a GDB built for the sparc target, whi= ch works pretty well when debugging by command line or using an old front-e= nd like DDD. But not with Eclipse or any modern front-end - and I assumed t= his would be due to the lack of support for the MI protocol by my GDBServer. So, are you saying that the gdb executable should be translating the "MI" c= ommands received by Eclipse CDT and sending them as CLI commands to my boar= d? Who has to "speak" MI? The GDBServer on my board or the gdb executable b= uilt for sparc target? Thanks again for your attention, Fabr=C3=ADcio. -----Mensagem original----- De: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] Em nome de Y= ao 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 th= e 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 interface. > > 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 gdb= for sparc target, use this gdb in Eclipse CDT, and connect to your old GDB= server. -- 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