Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: ILG.Robert <R.ILG@bachmann.info>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Extending RSP with vCont;n and vCont;f
Date: Fri, 04 Oct 2013 06:49:00 -0000	[thread overview]
Message-ID: <524E64AB.5040807@codesourcery.com> (raw)
In-Reply-To: <7E3A266F5548C442BC08FA3038B5197C68449231@ATFKEX06.bachmann.at>

On 10/02/2013 11:08 PM, ILG.Robert wrote:
> void
> _initialize_remote (void)
> {
> @@ -12168,6 +12274,34 @@
>                    &setlist,
>                    &showlist);
>
> +  add_setshow_boolean_cmd ("next-stepping", class_run,
> +                 &use_next_stepping, _("\
> +  Enable or disable next stepping."), _("\
> +  Show whether target-assisted next stepping is enabled."), _("\
> +  If on, and the target supports it, when skipping over a source line, GDB\n\
> +  tells the target to skip the next instruction itself instead of\n\
> +  of issuing multiple single-steps.  This speeds up source level\n\
> +  stepping.  If off, GDB always issues slower stepping mechanisms\n\
> +  instead, even if next stepping is supported by the target.  The default is on."),

Due to lack of description of these two packets, I have to understand
them from the help message of the command.

IIUC, it is similar to range-stepping, vCont;r except that start and 
stop address are not provided to the stub.  That means vCont;n requires 
a smarter stub to know enough line table information to decide where to 
stop.

An alternative to me is to teach your stub understand range stepping.

> +                 set_next_stepping,
> +                 show_next_stepping,
> +                 &setlist,
> +                 &showlist);
> +
> +  add_setshow_boolean_cmd ("finish-stepping", class_run,
> +                 &use_finish_stepping, _("\
> +  Enable or disable finish stepping."), _("\
> +  Show whether target-assisted finish stepping is enabled."), _("\
> +  If on, and the target supports it, when stepping out of a function, GDB\n\
> +  tells the target to step out of the corresponding stack frame itself.\n\
> +  This speeds up source level stepping. If off, GDB issues slower\n\
> +  stepping mechanisms instead, even if finish\n\
> +  stepping is supported by the target.  The default is on."),

GDB inserts a momentary breakpoint, resume the inferior and wait when
command "finish" is executed.  I don't think GDB emits a large number of 
RSP packets in this process.  Do you have an experiment that vCont;f
packet improves performance to some extent?

-- 
Yao (齐尧)


  parent reply	other threads:[~2013-10-04  6:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-02 15:08 ILG.Robert
2013-10-02 16:25 ` Eli Zaretskii
2013-10-04  6:49 ` Yao Qi [this message]
2013-10-03  5:04 ILG.Robert
2013-10-04 12:53 ILG.Robert
2013-10-06  7:58 ` Yao Qi
2013-10-07 12:05   ` Pedro Alves
2013-10-23  7:19 ILG.Robert
2013-11-08  8:18 ILG.Robert

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=524E64AB.5040807@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=R.ILG@bachmann.info \
    --cc=gdb-patches@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