public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Tom Tromey <tromey@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] Deprecate dbx mode
Date: Mon,  7 Mar 2022 17:44:04 +0000 (GMT)	[thread overview]
Message-ID: <20220307174404.35F4C385841F@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=cfeab26e4d42fb6f1bde429ab53a885a9d106a69

commit cfeab26e4d42fb6f1bde429ab53a885a9d106a69
Author: Tom Tromey <tromey@adacore.com>
Date:   Thu Mar 3 09:47:00 2022 -0700

    Deprecate dbx mode
    
    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.

Diff:
---
 gdb/NEWS   | 2 ++
 gdb/main.c | 3 +++
 2 files changed, 5 insertions(+)

diff --git a/gdb/NEWS b/gdb/NEWS
index 8fce31c41f1..ee9eaad63a0 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.  */


                 reply	other threads:[~2022-03-07 17:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220307174404.35F4C385841F@sourceware.org \
    --to=tromey@sourceware.org \
    --cc=gdb-cvs@sourceware.org \
    /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).