aboutsummaryrefslogtreecommitdiff
path: root/gdb/testsuite/gdb.rust
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2023-03-19 09:13:10 -0600
committerTom Tromey <tom@tromey.com>2023-03-20 07:47:15 -0600
commit6e7eef72164c00d6a5a7b0bce9fa01f5481f33cb (patch)
treee07c0c6a3e13a4d367fec7b44f025195a6368ff7 /gdb/testsuite/gdb.rust
parent0fea10f327466dbe949aef39cef5a6bdea91163f (diff)
downloadgdb-6e7eef72164c00d6a5a7b0bce9fa01f5481f33cb.zip
gdb-6e7eef72164c00d6a5a7b0bce9fa01f5481f33cb.tar.gz
gdb-6e7eef72164c00d6a5a7b0bce9fa01f5481f33cb.tar.bz2
Use rust_demangle to fix a crash
PR rust/30211 points out a crash caused by a particular completion. This turns out to happen because a Rust minsym winds up in a C++-specific path in strncmp_iw_with_mode, which ultimately causes the completer to pass invalid arguments to string::append. This patch fixes the bug by reordering the language constants so that Rust comes before C++, and then using rust_demangle. This ensures that minsyms are correctly marked as "Rust", avoiding this code and thus the crash. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=20367 Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30211 Reviewed-By: Andrew Burgess <aburgess@redhat.com>
Diffstat (limited to 'gdb/testsuite/gdb.rust')
-rw-r--r--gdb/testsuite/gdb.rust/methods.exp3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.rust/methods.exp b/gdb/testsuite/gdb.rust/methods.exp
index 8374ab1..72be6a1 100644
--- a/gdb/testsuite/gdb.rust/methods.exp
+++ b/gdb/testsuite/gdb.rust/methods.exp
@@ -59,3 +59,6 @@ gdb_test "print *self" " = 23"
gdb_test "info functions HasMethods::new" \
"fn methods::HasMethods::new\\(\\) -> methods::HasMethods;"
+# Regression test for PR rust/20367 and PR rust/30211. This used to
+# crash.
+gdb_test_no_output "complete break what"