From: Clifford Wolf <clifford@clifford.at>
To: Tristan Gingold <gingold@adacore.com>
Cc: gdb@sourceware.org
Subject: Re: Commands for a minimal GDB stub?
Date: Tue, 24 Nov 2015 14:38:00 -0000 [thread overview]
Message-ID: <20151124143811.GA10563@clifford.at> (raw)
In-Reply-To: <F6089B0E-C497-44B1-B184-715BF1E8BE44@adacore.com>
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!
kind regards,
- clifford
next prev parent reply other threads:[~2015-11-24 14:38 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 [this message]
2015-11-24 16:41 ` Tristan Gingold
2015-11-30 20:58 ` Juha Aaltonen
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=20151124143811.GA10563@clifford.at \
--to=clifford@clifford.at \
--cc=gdb@sourceware.org \
--cc=gingold@adacore.com \
/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).