Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "ILG.Robert" <R.ILG@bachmann.info>
Cc: gdb-patches@sourceware.org
Subject: Re: Extending RSP with vCont;n and vCont;f
Date: Wed, 02 Oct 2013 16:25:00 -0000	[thread overview]
Message-ID: <83y56bd4is.fsf@gnu.org> (raw)
In-Reply-To: <7E3A266F5548C442BC08FA3038B5197C68449231@ATFKEX06.bachmann.at>

> From: "ILG.Robert" <R.ILG@bachmann.info>
> Date: Wed, 2 Oct 2013 15:08:02 +0000
> 
> we would like to improve the RSP command "vCont" for remote debugging. It seems that the range option has been introduced recently to get rid of time consuming, successive single-steps. Our intention is to get rid of further, unnecessary RSP packages being sent as our target is capable to do a step-over (called next by GDB) and a step-return (called finish by GDB). Therefore we propose to extend the vCont command with "vCont;n" and "vCont;f" as well.

Thanks.

> +  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\
                                         ^^
Two spaces between sentences, please.


  reply	other threads:[~2013-10-02 16:25 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 [this message]
2013-10-04  6:49 ` Yao Qi
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=83y56bd4is.fsf@gnu.org \
    --to=eliz@gnu.org \
    --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