Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Pedro Alves <pedro@codesourcery.com>
Cc: teawater <teawater@gmail.com>, Eli Zaretskii <eliz@gnu.org>,
		gdb-patches@sourceware.org,
	Joel Brobecker <brobecker@adacore.com>,
		Michael Snyder <msnyder@vmware.com>
Subject: Re: [RFA] Displaced stepping just enable in non-stop mode
Date: Thu, 16 Oct 2008 02:39:00 -0000	[thread overview]
Message-ID: <20081016023837.GA32668@caradoc.them.org> (raw)
In-Reply-To: <200810160107.42525.pedro@codesourcery.com>

On Thu, Oct 16, 2008 at 01:07:42AM +0100, Pedro Alves wrote:
> Hi teawater,
> 
> Thanks again for doing this.  I believe your patch is close to being OK.  I
> took the liberty of adjusting it a bit, mostly re-wording a bit the
> comments and the documentation.
> 
> I think Joel's suggestion was a good one:  By gaining an "auto"
> setting, this is as much a maintainer command as
> "set breakpoint always-inserted" is.  So, I believe it's time we move
> the command to the top level "set" command group.
> 
>  set can-use-displaced-stepping (auto|on|off)
> 
> Eli, can I ask you to go over the help strings and the documentation in
> the patch below?  Do they look OK-ish?

That's a pretty long name.  Do you think there are any other useful
stepping related settings?  If so, maybe we should have a "set step"
prefix.

-- 
Daniel Jacobowitz
CodeSourcery


  parent reply	other threads:[~2008-10-16  2:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-07  6:27 teawater
2008-10-07 12:18 ` Joel Brobecker
2008-10-08  6:11   ` teawater
2008-10-09 14:50     ` Pedro Alves
2008-10-10  3:38       ` teawater
2008-10-14  7:36         ` teawater
2008-10-16  0:07           ` Pedro Alves
2008-10-16  2:29             ` teawater
2008-10-16  2:39             ` Daniel Jacobowitz [this message]
2008-10-16  2:59               ` Pedro Alves
2008-10-22  3:16                 ` teawater
2008-10-22 19:48                   ` Eli Zaretskii
2008-10-23  8:13                     ` teawater
2008-10-23 12:57                       ` Pedro Alves
2008-10-24  2:49                         ` teawater
2008-10-16  8:13             ` Eli Zaretskii
2008-10-16 12:35               ` Daniel Jacobowitz
2008-10-16 18:27                 ` Eli Zaretskii
2008-10-16 18:33                   ` Daniel Jacobowitz
2008-10-16 21:19                     ` Michael Snyder
2008-10-17  5:46                       ` teawater
2008-10-17 10:02                         ` Eli Zaretskii
2008-10-17 15:05                           ` Pedro Alves
2008-10-17 16:09                           ` teawater
2008-10-17 14:48                       ` Pedro Alves
2008-10-17 16:01                         ` teawater
2008-10-17 17:33                         ` Michael Snyder
2008-10-17 19:47                           ` Jakob Engblom
2008-10-17 19:49                             ` Michael Snyder
2008-10-17 14:51                   ` Pedro Alves
2008-10-17 15:53                     ` Eli Zaretskii

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=20081016023837.GA32668@caradoc.them.org \
    --to=drow@false.org \
    --cc=brobecker@adacore.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=msnyder@vmware.com \
    --cc=pedro@codesourcery.com \
    --cc=teawater@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