From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: teawater <teawater@gmail.com>,
"Joel Brobecker" <brobecker@adacore.com>,
"Michael Snyder" <msnyder@vmware.com>
Subject: Re: [RFA] Displaced stepping just enable in non-stop mode
Date: Thu, 09 Oct 2008 14:50:00 -0000 [thread overview]
Message-ID: <200810091549.26712.pedro@codesourcery.com> (raw)
In-Reply-To: <daef60380810072310n1397d03ct8af799c7f3600a06@mail.gmail.com>
Hi,
Thanks for doing this.
On Wednesday 08 October 2008 07:10:43, teawater wrote:
> -int can_use_displaced_stepping = 1;
> +const char can_use_displaced_stepping_auto[] = "auto";
> +const char can_use_displaced_stepping_on[] = "on";
> +const char can_use_displaced_stepping_off[] = "off";
> +const char *can_use_displaced_stepping_enum[] =
> +{
> + can_use_displaced_stepping_auto,
> + can_use_displaced_stepping_on,
> + can_use_displaced_stepping_off,
> + NULL,
> +};
> +const char *can_use_displaced_stepping = can_use_displaced_stepping_auto;
Could you make these static while you're at it, please? It was just missed
in the old boolean setting.
> static void
> show_can_use_displaced_stepping (struct ui_file *file, int from_tty,
> struct cmd_list_element *c,
> @@ -567,12 +579,16 @@ Debugger's willingness to use displaced
> "breakpoints is %s.\n"), value);
Could you update this function to show what effect the auto setting
is currently having? See breakpoint.c:show_always_inserted_mode for
an example.
> }
>
> -/* Return non-zero if displaced stepping is enabled, and can be used
> +/* Return non-zero if displaced stepping is auto, and can be used
> + with GDBARCH, and in non-stop mode.
> + Return non-zero if displaced stepping is on, and can be used
> with GDBARCH. */
> static int
> use_displaced_stepping (struct gdbarch *gdbarch)
> {
> - return (can_use_displaced_stepping
> + return (((can_use_displaced_stepping == can_use_displaced_stepping_auto
> + && non_stop)
> + || can_use_displaced_stepping == can_use_displaced_stepping_on)
> && gdbarch_displaced_step_copy_insn_p (gdbarch));
> }
>
> @@ -4857,11 +4873,14 @@ function is skipped and the step command
> show_step_stop_if_no_debug,
> &setlist, &showlist);
>
> - add_setshow_boolean_cmd ("can-use-displaced-stepping", class_maintenance,
> + add_setshow_enum_cmd ("can-use-displaced-stepping", class_maintenance,
> + can_use_displaced_stepping_enum,
> &can_use_displaced_stepping, _("\
> Set debugger's willingness to use displaced stepping."), _("\
> Show debugger's willingness to use displaced stepping."), _("\
> -If zero, gdb will not use displaced stepping to step over\n\
> +If auto, gdb will auto use displaced stepping if it need (in non-stop mode).\n\
> +If on, gdb will use displaced stepping if such is supported by the target.\n\
> +If off, gdb will not use displaced stepping to step over\n\
> breakpoints, even if such is supported by the target."),
This also needs to be updated in the manual. I'd suggest borrowing the text
from breakpoint.c's "always-inserted" command description to make it a
bit more descriptive, and mention which mode is the default. Should mostly
be a matter of copy-paste, I think.
--
Pedro Alves
next prev parent reply other threads:[~2008-10-09 14:50 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 [this message]
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
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=200810091549.26712.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=msnyder@vmware.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