From: Joel Brobecker <brobecker@adacore.com>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org, Jerome Guitton <guitton@adacore.com>
Subject: Re: [RFA] arm-pikeos: software single step
Date: Fri, 14 Sep 2018 00:38:00 -0000 [thread overview]
Message-ID: <20180914003753.GA16818@adacore.com> (raw)
In-Reply-To: <9ff1cf95-0ec4-dd58-6445-4fd51730a7d8@redhat.com>
> Almost. GDB can't trust "vCont;c;C" alone, because for a long
> while GDBserver would send "vCont;c;s;C;S" even if the target
> did not support hardware stepping. So what a stub needs to do
> is:
>
> Return "vCont;c;C" to "vCont?" _AND_ include "vContSupported"
> in the reported "qSupported" features. The latter tells GDB
> to trust that the actions included in "vCont?" are really the
> supported ones. (I wish we had implemented this a little bit
> differently, but that ship has sailed, and although a bit
> cumbersome, it works.)
Excellent. I've passed that information in what is hopefully
a concise and clear message that JeromeG can pass to Sysgo.
Hopefully something will come out of it.
Thanks Pedro!
--
Joel
prev parent reply other threads:[~2018-09-14 0:38 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-10 15:13 Joel Brobecker
2018-09-10 17:28 ` Tom Tromey
2018-09-10 17:43 ` Joel Brobecker
2018-09-10 18:39 ` [RFA v2] " y
2018-09-10 20:01 ` Simon Marchi
2018-09-10 20:53 ` Tom Tromey
2018-09-11 8:56 ` Joel Brobecker
2018-09-11 9:58 ` Simon Marchi
2018-09-11 13:51 ` Joel Brobecker
2018-09-11 15:41 ` Tom Tromey
2018-09-11 21:17 ` Joel Brobecker
2018-09-14 0:47 ` Joel Brobecker
2018-09-14 10:57 ` Simon Marchi
2018-11-01 21:44 ` Joel Brobecker
2018-09-11 9:08 ` [RFA] " Pedro Alves
2018-09-11 11:04 ` Joel Brobecker
2018-09-11 11:27 ` Pedro Alves
2018-09-11 20:57 ` Joel Brobecker
2018-09-12 13:22 ` Pedro Alves
2018-09-14 0:38 ` Joel Brobecker [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=20180914003753.GA16818@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@adacore.com \
--cc=palves@redhat.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