From: Philippe Waroquiers <philippe.waroquiers@skynet.be>
To: gdb-patches@sourceware.org
Subject: [PUSHED/OBVIOUS] Remove gdb-gdb.gdb breakpoint on disappeared function info_command.
Date: Fri, 1 May 2020 16:54:51 +0200 [thread overview]
Message-ID: <20200501145451.20119-1-philippe.waroquiers@skynet.be> (raw)
The function info_command has disappeared, so this breakpoint does not
work anymore.
"info_command" was a function for the prefix command "info",
giving the list of "info" subcommands.
It is not very clear what the removed breakpoint and its associated
command list was supposed to do.
Removed and pushed as obvious, after discussion with Tom.
---
gdb/ChangeLog | 4 ++++
gdb/gdb-gdb.gdb.in | 6 ------
2 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/gdb/ChangeLog b/gdb/ChangeLog
index 4f3b2680bb..ee4f3a74c0 100644
--- a/gdb/ChangeLog
+++ b/gdb/ChangeLog
@@ -1,3 +1,7 @@
+2020-05-01 Philippe Waroquiers <philippe.waroquiers@skynet.be>
+ * gdb-gdb.gdb-in: Remove breakpoint on disappeared function
+ info_command.
+
2020-04-30 Kamil Rytarowski <n54@gmx.com>
* nbsd-nat.c (nbsd_enable_proc_events)
diff --git a/gdb/gdb-gdb.gdb.in b/gdb/gdb-gdb.gdb.in
index 05a38b2670..b647445e8c 100644
--- a/gdb/gdb-gdb.gdb.in
+++ b/gdb/gdb-gdb.gdb.in
@@ -7,12 +7,6 @@ if !$gdb_init_done
b internal_error
- b info_command
- commands
- silent
- return
- end
-
dir @srcdir@/../libiberty
dir @srcdir@/../bfd
dir @srcdir@
--
2.20.1
next reply other threads:[~2020-05-01 14:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-01 14:54 Philippe Waroquiers [this message]
2020-05-02 4:02 ` Kevin Buettner
2020-05-02 21:19 ` Maciej W. Rozycki
2020-05-02 23:01 ` Philippe Waroquiers
2020-05-02 23:57 ` Kevin Buettner
2020-05-03 0:13 ` Maciej W. Rozycki
2020-05-03 0:33 ` Simon Marchi
2020-05-03 11:03 ` Pedro Alves
2020-05-03 12:45 ` Philippe Waroquiers
2020-05-03 17:17 ` Tom Tromey
2020-05-03 18:33 ` Philippe Waroquiers
2020-05-04 21:21 ` 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=20200501145451.20119-1-philippe.waroquiers@skynet.be \
--to=philippe.waroquiers@skynet.be \
--cc=gdb-patches@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