From: "Breazeal, Don" <donb@codesourcery.com>
To: "Fabrício de Novaes Kucinskis" <fabricio@dea.inpe.br>,
gdb@sourceware.org
Subject: Re: RES: How to update an old GDBServer to implement gdb/mi?
Date: Mon, 23 Jun 2014 15:45:00 -0000 [thread overview]
Message-ID: <53A84B9C.4000204@codesourcery.com> (raw)
In-Reply-To: <002301cf8ef2$6af896e0$40e9c4a0$@dea.inpe.br>
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
>
next prev parent reply other threads:[~2014-06-23 15:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-21 0:52 Fabricio de Novaes Kucinskis
2014-06-21 1:11 ` Yao Qi
2014-06-23 14:51 ` RES: " Fabrício de Novaes Kucinskis
2014-06-23 15:45 ` Breazeal, Don [this message]
2014-06-24 13:56 ` RES: " Fabrício de Novaes Kucinskis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53A84B9C.4000204@codesourcery.com \
--to=donb@codesourcery.com \
--cc=fabricio@dea.inpe.br \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox