This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH 2/2] Enable range stepping for ARM on GDBServer
- From: Antoine Tremblay <antoine dot tremblay at ericsson dot com>
- To: Pedro Alves <palves at redhat dot com>, Yao Qi <qiyaoltc at gmail dot com>
- Cc: Antoine Tremblay <antoine dot tremblay at ericsson dot com>, <gdb-patches at sourceware dot org>
- Date: Thu, 1 Sep 2016 11:21:46 -0400
- Subject: Re: [PATCH 2/2] Enable range stepping for ARM on GDBServer
- Authentication-results: sourceware.org; auth=none
- References: <20160831171406.24057-1-antoine.tremblay@ericsson.com> <20160831171406.24057-2-antoine.tremblay@ericsson.com> <b5bc1e35-1840-a7ab-6392-cb29c4ee4b8f@redhat.com> <wwokwpiwyfct.fsf@ericsson.com> <3fdb7193-60c7-49c9-ccf5-bc040aa157ea@redhat.com> <wwoktwe0ycml.fsf@ericsson.com> <a44c8554-cc86-6ed1-b5cf-0697189eca73@redhat.com>
Pedro Alves writes:
> On 08/31/2016 08:14 PM, Antoine Tremblay wrote:
>
>> I'm sorry I can't be more helpful at the moment but I wanted to post
>> this issue before I have to leave for a while.
>
> Understood. Does enabling range stepping unblock something else?
It would unblock ARM tracepoints, as per Yao's requirements...
>
>> However I wonder if range stepping or ARM depends on this of if we
>> should treat it as two different issues ?
>
> Offhand, the knee-jerk reaction is that if enabling range stepping
> causes a regression, then it sounds like range stepping has a
> problem that should be fixed and it may be premature to enable it.
>
> I see a parallel here with all the all-stop-on-top-of-non-stop
> work, which exposed a ton of such latent problems that were treated
> as dependencies that needed to be addressed first. That's what
> resulted in the creation of this test (see 'git log ede9f622af1f').
>
> as-ns is enabled by default on native, but not on remote. It sounds
> like testing with as-ns enabled on remote could reveal the same
> range stepping problems, but all over the testsuite instead. :-/
>
I see, in that sense we could consider it unsupported for now in remote
and fix it along the rest of the issues as non-stop gains support ?
Yao any comments on this?
Thanks,
Antoine