From: Pedro Alves <pedro@palves.net>
To: Tom Tromey <tromey@adacore.com>, gdb-patches@sourceware.org
Subject: Re: [RFC] Deprecate dbx mode
Date: Thu, 3 Mar 2022 17:36:51 +0000 [thread overview]
Message-ID: <481bef24-a3f3-8d43-c46b-49e383a1f33a@palves.net> (raw)
In-Reply-To: <20220303170425.467663-1-tromey@adacore.com>
+1. Honestly, I've never heard of anyone using this mode.
May want to announce this in the more user-facing gdb list, just in case, though.
Pedro Alves
On 2022-03-03 17:04, Tom Tromey via Gdb-patches wrote:
> GDB has a dbx emulation mode that adds a few aliases and helper
> commands. This mode is barely documented and is very superficial
> besides. I suspect it is rarely used, and I would like to propose
> deprecating it for GDB 12, and then removing it in GDB 13.
> ---
> gdb/NEWS | 2 ++
> gdb/main.c | 3 +++
> 2 files changed, 5 insertions(+)
>
> diff --git a/gdb/NEWS b/gdb/NEWS
> index dc2cac1871b..0b75a4a50bd 100644
> --- a/gdb/NEWS
> +++ b/gdb/NEWS
> @@ -3,6 +3,8 @@
>
> *** Changes since GDB 11
>
> +* DBX mode is deprecated, and will be removed in GDB 13
> +
> * Improved C++ template support
>
> GDB now treats functions/types involving C++ templates like it does function
> diff --git a/gdb/main.c b/gdb/main.c
> index 8f944d86545..73fdff25018 100644
> --- a/gdb/main.c
> +++ b/gdb/main.c
> @@ -1028,6 +1028,9 @@ captured_main_1 (struct captured_main_args *context)
> }
> }
>
> + if (dbx_commands)
> + warning (_("--dbx mode is deprecated and will be removed"));
> +
> save_original_signals_state (quiet);
>
> /* Try to set up an alternate signal stack for SIGSEGV handlers. */
prev parent reply other threads:[~2022-03-03 17:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 17:04 Tom Tromey
2022-03-03 17:36 ` Pedro Alves [this message]
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=481bef24-a3f3-8d43-c46b-49e383a1f33a@palves.net \
--to=pedro@palves.net \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).