aboutsummaryrefslogtreecommitdiff
path: root/gdb/dwarf2
diff options
context:
space:
mode:
authorTom Tromey <tromey@adacore.com>2023-03-07 11:25:58 -0700
committerTom Tromey <tromey@adacore.com>2023-03-07 11:30:20 -0700
commit4779ed9757fa71e6743fb7fc1f9eeae8267ae36c (patch)
treea27f73da494be22cee37c4013053a9fa3d967144 /gdb/dwarf2
parent74f1d7f4a3183bca13058dde29f5559d480a1b51 (diff)
downloadgdb-4779ed9757fa71e6743fb7fc1f9eeae8267ae36c.zip
gdb-4779ed9757fa71e6743fb7fc1f9eeae8267ae36c.tar.gz
gdb-4779ed9757fa71e6743fb7fc1f9eeae8267ae36c.tar.bz2
Fix selfcheck regression due to new maint command
Simon points out that the new maint command, intended to fix a regression, also introduces a new regression in "maint selftest". This patch fixes the error. I did a full regression test on x86-64 Fedora 36.
Diffstat (limited to 'gdb/dwarf2')
-rw-r--r--gdb/dwarf2/cooked-index.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gdb/dwarf2/cooked-index.c b/gdb/dwarf2/cooked-index.c
index d09faed..3a90769 100644
--- a/gdb/dwarf2/cooked-index.c
+++ b/gdb/dwarf2/cooked-index.c
@@ -659,8 +659,8 @@ _initialize_cooked_index ()
add_cmd ("wait-for-index-cache", class_maintenance,
maintenance_wait_for_index_cache, _("\
-Usage: maintenance wait-for-index-cache\n\
-Wait until all pending writes to the index cache have completed."),
+Wait until all pending writes to the index cache have completed.\n\
+Usage: maintenance wait-for-index-cache"),
&maintenancelist);
gdb::observers::gdb_exiting.attach (wait_for_index_cache, "cooked-index");