Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Christian Biesinger <cbiesinger@google.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Restore info_command and breakpoint
Date: Tue, 5 May 2020 13:26:11 -0500	[thread overview]
Message-ID: <CAPTJ0XHH+FeoDjJTgf6zkU9qJfjwd2aOi+t3_eOSN10=JUsbSQ@mail.gmail.com> (raw)
In-Reply-To: <20200505170249.31630-1-tromey@adacore.com>

On Tue, May 5, 2020 at 12:03 PM Tom Tromey <tromey@adacore.com> wrote:
>
> As discussed on gdb-patches, this restores info_command and the
> breakpoint on info_command in gdb-gdb.gdb.  This reverts a tiny part
> of 0743fc83c03 ("Replace most calls to help_list and cmd_show_list"),
> as well as 652fc23a30a ("Remove gdb-gdb.gdb breakpoint on disappeared
> function info_command.").
>
> gdb/ChangeLog
> 2020-05-05  Tom Tromey  <tromey@adacore.com>
>
>         * cli/cli-cmds.c (info_command): Restore.
>         (_initialize_cli_cmds): Use add_prefix_command for "info".
>         * gdb-gdb.gdb.in: Restore breakpoint on info_command.
> ---
>  gdb/ChangeLog      |  6 ++++++
>  gdb/cli/cli-cmds.c | 15 +++++++++++++--
>  gdb/gdb-gdb.gdb.in |  6 ++++++
>  3 files changed, 25 insertions(+), 2 deletions(-)
>
> diff --git a/gdb/cli/cli-cmds.c b/gdb/cli/cli-cmds.c
> index 1b677f5d7a1..104d273812f 100644
> --- a/gdb/cli/cli-cmds.c
> +++ b/gdb/cli/cli-cmds.c
> @@ -191,6 +191,17 @@ error_no_arg (const char *why)
>    error (_("Argument required (%s)."), why);
>  }
>
> +/* This implements the "info" prefix command.  Normally such commands
> +   are automatically handled by add_basic_prefix_cmd, but in this case
> +   a separate command is used so that it can be hooked into by
> +   gdb-gdb.gdb.  */
> +
> +static void
> +info_command (const char *arg, int from_tty)
> +{
> +  help_list (infolist, "info ", all_commands, gdb_stdout);
> +}
> +
>  /* See cli/cli-cmds.h.  */
>
>  void
> @@ -2189,9 +2200,9 @@ Without an argument, history expansion is enabled."),
>                            show_history_expansion_p,
>                            &sethistlist, &showhistlist);
>
> -  add_basic_prefix_cmd ("info", class_info, _("\
> +  add_prefix_cmd ("info", class_info, info_command, _("\
>  Generic command for showing things about the program being debugged."),
> -                       &infolist, "info ", 0, &cmdlist);
> +                 &infolist, "info ", 0, &cmdlist);
>    add_com_alias ("i", "info", class_info, 1);
>    add_com_alias ("inf", "info", class_info, 1);
>
> diff --git a/gdb/gdb-gdb.gdb.in b/gdb/gdb-gdb.gdb.in
> index b647445e8c9..05a38b2670b 100644
> --- a/gdb/gdb-gdb.gdb.in
> +++ b/gdb/gdb-gdb.gdb.in
> @@ -7,6 +7,12 @@ if !$gdb_init_done
>
>    b internal_error
>
> +  b info_command

It would probably be good to add a comment here?
# This provides an easy way to break into the top-level GDB by typing "info"

> +  commands
> +    silent
> +    return
> +  end
> +
>    dir @srcdir@/../libiberty
>    dir @srcdir@/../bfd
>    dir @srcdir@
> --
> 2.21.1
>


  reply	other threads:[~2020-05-05 18:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-05 17:02 Tom Tromey
2020-05-05 18:26 ` Christian Biesinger [this message]
2020-05-05 18:51   ` Philippe Waroquiers
2020-05-05 19:00     ` Tom Tromey
2020-05-05 19:00   ` Tom Tromey
2020-05-11 21: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='CAPTJ0XHH+FeoDjJTgf6zkU9qJfjwd2aOi+t3_eOSN10=JUsbSQ@mail.gmail.com' \
    --to=cbiesinger@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@adacore.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