From: Juha Aaltonen <turbopultti@gmail.com>
To: gdb-mailing list <gdb@sourceware.org>
Subject: Re: Commands for a minimal GDB stub?
Date: Mon, 30 Nov 2015 20:58:00 -0000 [thread overview]
Message-ID: <CAHR0xd5dUNuofwKwi9wJKar5CY5MPZtAaH5=es42VivSWnNTig@mail.gmail.com> (raw)
In-Reply-To: <4EF38853-B93D-4E56-AA2D-E2AA3D0089E5@adacore.com>
In case it's of any help, I've been writing a bit more than minimal
bare metal standalone stub/server/agent/whatchacallit for Raspberry Pi
2B (Cortex-A7).
It might be helpful if you are wondering about details of the remote
serial protocol.
https://github.com/turboscrew/rpi_stub
On Tue, Nov 24, 2015 at 6:41 PM, Tristan Gingold <gingold@adacore.com> wrote:
>
>> On 24 Nov 2015, at 15:38, Clifford Wolf <clifford@clifford.at> wrote:
>>
>> On Tue, Nov 24, 2015 at 02:51:49PM +0100, Tristan Gingold wrote:
>>> I think the documentation is slightly incorrect. For an almost minimal
>>> gdb stub, I have also implemented:
>>> ?, z, Z, qSupported, qC, qSymbol::, P, k, H
>>> z, Z, H, k, qSupported returned $#00.
>>>
>>> You shouldn’t be very far from having a communication.
>>
>> thanks. I've now added 'S05' as response to '?' and now I get to the point
>> where gdb actually queries the register file using the 'g' command. So I
>> think I'm now where the actual work starts.. ;)
>>
>> again, thanks a lot for your help!
>
> You’re welcome. Note there are a few examples of stubs within gdb/stubs.
>
> Tristan.
>
prev parent reply other threads:[~2015-11-30 20:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 13:38 Clifford Wolf
2015-11-24 13:51 ` Tristan Gingold
2015-11-24 14:38 ` Clifford Wolf
2015-11-24 16:41 ` Tristan Gingold
2015-11-30 20:58 ` Juha Aaltonen [this message]
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='CAHR0xd5dUNuofwKwi9wJKar5CY5MPZtAaH5=es42VivSWnNTig@mail.gmail.com' \
--to=turbopultti@gmail.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).