public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Mathieu Tarral <mathieu.tarral@protonmail.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Minimum set of actions to support vCont
Date: Fri, 23 Nov 2018 10:17:00 -0000	[thread overview]
Message-ID: <mpwybaShdcjqwDYecd26eDmMXanC6zWs3o_dZD4vcWWEsbmbsAtsQihuSZFku7knyjcH0UCFl43cDQpHrCUEgtPlIPmACZ_MgralRTzzqws=@protonmail.com> (raw)

Hi,

I'm implementing the vCont packet in my stub,
and so far, when I receive a vCont? packet, I reply with
"vCont;c;s" since I support singlestep and continue.

This implementation works in radare2, but it doesn't work with GDB:
Sending packet: $vCont?#49...Packet received: vCont;c;s
Packet vCont (verbose-resume) is NOT supported

What is the minimal set of actions required to support
vCont in GDB RSP ?


Thanks.
--
Mathieu Tarral

Sent with ProtonMail Secure Email.

             reply	other threads:[~2018-11-23 10:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-23 10:17 Mathieu Tarral [this message]
2018-12-11 17:01 ` Simon Marchi

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='mpwybaShdcjqwDYecd26eDmMXanC6zWs3o_dZD4vcWWEsbmbsAtsQihuSZFku7knyjcH0UCFl43cDQpHrCUEgtPlIPmACZ_MgralRTzzqws=@protonmail.com' \
    --to=mathieu.tarral@protonmail.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).