From: Antoine Tremblay <antoine.tremblay@ericsson.com>
To: <gdb-patches@sourceware.org>, Yao Qi <qiyaoltc@gmail.com>
Subject: Re: [PATCH 1/2] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step
Date: Fri, 04 Sep 2015 14:40:00 -0000 [thread overview]
Message-ID: <55E9AD46.9070002@ericsson.com> (raw)
In-Reply-To: <55E8638C.1010806@ericsson.com>
On 09/03/2015 11:13 AM, Antoine Tremblay wrote:
>
>
> On 09/02/2015 03:22 PM, Antoine Tremblay wrote:
>>
>> On 09/01/2015 04:41 AM, Yao Qi wrote:
>>> In my patch https://sourceware.org/ml/gdb-patches/2015-04/msg01110.html
>>> a new target_ops hook supports_conditional_breakpoints was added to
>>> disable conditional breakpoints if target doesn't have hardware single
>>> step. This patch is to generalize this hook from
>>> supports_conditional_breakpoints to supports_hardware_single_step,
>>> so that the following patch can use it.
>>>
>>
>> Could we generalize this even more to supports_single_step like your
>> next patch ?
>>
>> Since I'm working on software single stepping for ARM, if this patch
>> goes in I'll need to implement a supports_software_single_step and
>> enable ConditionalBreakpoints for this case too...
>>
>> Is there a need to know that it's really hardware or just knowing that
>> it can single step would be ok ?
>>
>
> Note also that this way would force supports_conditional_breakpoints to
> check for more than can_hardware_single_step and require a target
> function set manually to 1 on targets that we know have a proper
> software or hardware single step like :
>
> static int
> linux_supports_conditional_breakpoints (void)
> {
> return the_low_target.supports_conditional_breakpoints ();
> }
>
> I had initially added that in my set but we could change it for
> the_low_target_.can_single_step () ?
>
> This way targets that have proper software single step can be handled.
> Otherwise every software single step implementation is deemed too simple
> to be used...
>
> Would that seem ok ?
>
>
After more analysis, I think ConditionalBreakpoints should be enabled
for software/hardware single step.
But for the vCont s:S I don't think we can assume that gdbserver's
software single step is better then GDB's, it should be the opposite.
So it should only be enabled when hardware single step is present so we
can't do away with supports_hardware_single_step.
So to support all features I suggest we have in GDBServer :
supports_hardware_single_step
supports_software_single_step
Enable ConditionalBreakpoints for supports_hardware_single_step ||
supports_software_single_step
And enable vCont s:s only for supports_hardware_single_step
I can add the supports_software_single_step in my patchset..
Does that sounds right ? So your current patch would be fine..
next prev parent reply other threads:[~2015-09-04 14:40 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 8:42 [PATCH 0/2 V2] Support single step by arch or target Yao Qi
2015-09-01 8:42 ` [PATCH 2/2] " Yao Qi
2015-09-01 13:18 ` Antoine Tremblay
2015-09-01 14:23 ` Yao Qi
2015-09-01 15:30 ` Antoine Tremblay
2015-09-01 14:40 ` Eli Zaretskii
2015-09-04 14:46 ` Antoine Tremblay
2015-09-14 8:18 ` Yao Qi
2015-09-15 13:31 ` Pedro Alves
2015-09-01 8:42 ` [PATCH 1/2] [gdbserver] Rename supports_conditional_breakpoints to supports_hardware_single_step Yao Qi
2015-09-02 19:22 ` Antoine Tremblay
2015-09-03 15:13 ` Antoine Tremblay
2015-09-04 14:40 ` Antoine Tremblay [this message]
2015-09-04 15:04 ` Antoine Tremblay
2015-09-08 14:32 ` Yao Qi
2015-09-08 19:01 ` Antoine Tremblay
2015-09-09 15:37 ` Antoine Tremblay
2015-09-15 13:11 ` [PATCH 0/2 V2] Support single step by arch or target Yao Qi
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=55E9AD46.9070002@ericsson.com \
--to=antoine.tremblay@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=qiyaoltc@gmail.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