From: Pedro Alves <palves@redhat.com>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org, Jerome Guitton <guitton@adacore.com>
Subject: Re: [RFA] arm-pikeos: software single step
Date: Tue, 11 Sep 2018 11:27:00 -0000 [thread overview]
Message-ID: <15fd4c1d-d265-073d-a4d8-14de3d607a44@redhat.com> (raw)
In-Reply-To: <20180911110417.GB3379@adacore.com>
On 09/11/2018 12:04 PM, Joel Brobecker wrote:
> Hi Pedro,
>
>> It seems to me we can take a better approach here, that eliminates
>> this particular problem not just for PikeOS, but for all other cases
>> of random RTOS's.
>>
>> That is, you should be able to make your stub tell GDB that it
>> can or can't hardware single step, and then GDB adjusts itself.
>
> Unfortunately, the problem is that we do not control the stub (muxa),
> it is a tool that the vendor provides.
Did you check whether it is already reporting the RSP packets as I
had suggested? We wouldn't be adding new packets, but instead using
some that are already defined.
If the stub really needs modification, I'm not opposed to your patch
as stop gap. Would there be any chance to forward the information to
the sysgo folks, see if they're willing to tweak the stub? It should
be a trivial change.
IWBN to fix the infrastructure, so that the next time a similar
patch comes in we could just "no, fix your stub". :-)
Thanks,
Pedro Alves
next prev parent reply other threads:[~2018-09-11 11:27 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 [this message]
2018-09-11 20:57 ` Joel Brobecker
2018-09-12 13:22 ` Pedro Alves
2018-09-14 0:38 ` Joel Brobecker
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=15fd4c1d-d265-073d-a4d8-14de3d607a44@redhat.com \
--to=palves@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=guitton@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