RES: RES: How to update an old GDBServer to implement gdb/mi?

Fabrício de Novaes Kucinskis fabricio@dea.inpe.br
Tue Jun 24 13:56:00 GMT 2014


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 (and maybe one or two commands absent from our GDBServer implementation...).

Regards,

Fabrício.


-----Mensagem original-----
De: gdb-owner@sourceware.org [mailto:gdb-owner@sourceware.org] Em nome de Breazeal, Don
Enviada em: segunda-feira, 23 de junho de 2014 12:46
Para: Fabrício 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ício 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 Server 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. There's no operating system under the GDB Server.
>
> On the gdb "host" side, I already use a GDB built for the sparc target, which 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 GDBServer.
>
> 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 board? Who has to "speak" MI? The GDBServer on my board or the gdb executable built for sparc target?
>
> Thanks again for your attention,
>
> Fabrício.

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 <== MI ==> GDB <== RSP ==> GDBserver

MI support should already be built in to your GDB executable, you can try it 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 the 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 GDBserver.
>
> --
> Yao (齐尧)
>
>
> ---
> Este email está limpo de vírus e malwares porque a proteção do avast! Antivírus está ativa.
> http://www.avast.com
>



---
Este email está limpo de vírus e malwares porque a proteção do avast! Antivírus está ativa.
http://www.avast.com



More information about the Gdb mailing list