Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@google.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [pushed] Restore some windows-tdep.c code
Date: Sat, 18 Apr 2020 20:43:31 -0500	[thread overview]
Message-ID: <CAPTJ0XE6Yr0+Y+n6v-PqndUiLCcgwZYHxk8hGS9nQoMDrJscLw@mail.gmail.com> (raw)
In-Reply-To: <20200419014112.22277-1-tom@tromey.com>

On Sat, Apr 18, 2020, 20:41 Tom Tromey <tom@tromey.com> wrote:

> When I removed init_w32_command_list, I weirdly neglected to see if it
> was called anywhere else.  This patch restores the function, which is
> called from windows-nat.c.  Sorry about the breakage.
>
> Is it possible to have a windows-native gdb that isn't also using
> windows-tdep?
>
> Anyway, I'm checking this in.
>
> gdb/ChangeLog
> 2020-04-18  Tom Tromey  <tom@tromey.com>
>
>         * windows-tdep.c (init_w32_command_list)
>         (w32_prefix_command_valid): Restore.
>         (_initialize_windows_tdep): Call init_w32_command_list.
> ---
>  gdb/ChangeLog      |  6 ++++++
>  gdb/windows-tdep.c | 20 ++++++++++++++++----
>  2 files changed, 22 insertions(+), 4 deletions(-)
>
> diff --git a/gdb/windows-tdep.c b/gdb/windows-tdep.c
> index 4af797f9469..e2b7960829f 100644
> --- a/gdb/windows-tdep.c
> +++ b/gdb/windows-tdep.c
> @@ -602,6 +602,21 @@ show_maint_show_all_tib (struct ui_file *file, int
> from_tty,
>                             "Thread Information Block is %s.\n"), value);
>  }
>
> +
> +static int w32_prefix_command_valid = 0;
> +void
> +init_w32_command_list (void)
> +{
> +  if (!w32_prefix_command_valid)
> +    {
> +      add_basic_prefix_cmd
> +       ("w32", class_info,
> +        _("Print information specific to Win32 debugging."),
> +        &info_w32_cmdlist, "info w32 ", 0, &infolist);
> +      w32_prefix_command_valid = 1;
>

Seems like this could be made a bool.

+    }
> +}
> +
>  /* Implementation of `gdbarch_gdb_signal_to_target' for Windows.  */
>
>  static int
> @@ -1077,10 +1092,7 @@ _initialize_windows_tdep ()
>    windows_gdbarch_data_handle
>      = gdbarch_data_register_post_init (init_windows_gdbarch_data);
>
> -  add_basic_prefix_cmd ("w32", class_info,
> -                       _("Print information specific to Win32
> debugging."),
> -                       &info_w32_cmdlist, "info w32 ", 0, &infolist);
> -
> +  init_w32_command_list ();
>    add_cmd ("thread-information-block", class_info, display_tib,
>            _("Display thread information block."),
>            &info_w32_cmdlist);
> --
> 2.17.2
>
>


  reply	other threads:[~2020-04-19  1:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-19  1:41 Tom Tromey
2020-04-19  1:43 ` Christian Biesinger [this message]
2020-04-19 15:28   ` Tom Tromey

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=CAPTJ0XE6Yr0+Y+n6v-PqndUiLCcgwZYHxk8hGS9nQoMDrJscLw@mail.gmail.com \
    --to=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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