aboutsummaryrefslogtreecommitdiff
path: root/gdb/rust-parse.c
diff options
context:
space:
mode:
authorTom Tromey <tom@tromey.com>2023-03-02 07:44:11 -0700
committerTom Tromey <tom@tromey.com>2024-01-28 10:58:16 -0700
commit974b36c2ae2b351d022cc62579656f722da6e17a (patch)
tree1d7d813ffba23ac283f502e655460d52156a7d18 /gdb/rust-parse.c
parent10d6e9413e7ab9b30fbdb69e03262dc327831f84 (diff)
downloadgdb-974b36c2ae2b351d022cc62579656f722da6e17a.zip
gdb-974b36c2ae2b351d022cc62579656f722da6e17a.tar.gz
gdb-974b36c2ae2b351d022cc62579656f722da6e17a.tar.bz2
Use the new symbol domains
This patch changes the DWARF reader to use the new symbol domains. It also adjusts many bits of associated code to adapt to this change. The non-DWARF readers are updated on a best-effort basis. This is somewhat simpler since most of them only support C and C++. I have no way to test a few of these. I went back and forth a few times on how to handle the "tag" situation. The basic problem is that C has a special namespace for tags, which is separate from the type namespace. Other languages don't do this. So, the question is, should a DW_TAG_structure_type end up in the tag domain, or the type domain, or should it be language-dependent? I settled on making it language-dependent using a thought experiment. Suppose there was a Rust compiler that only emitted nameless DW_TAG_structure_type objects, and specified all structure type names using DW_TAG_typedef. This DWARF would be correct, in that it faithfully represents the source language -- but would not work with a purely struct-domain implementation in gdb. Therefore gdb would be wrong. Now, this approach is a little tricky for C++, which uses tags but also enters a typedef for them. I notice that some other readers -- like stabsread -- actually emit a typedef symbol as well. And, I think this is a reasonable approach. It uses more memory, but it makes the internals simpler. However, DWARF never did this for whatever reason, and so in the interest of keeping the series slightly shorter, I've left some C++-specific hacks in place here. Note that this patch includes language_minimal as a language that uses tags. I did this to avoid regressing gdb.dwarf2/debug-names-tu.exp, which doesn't specify the language for a type unit. Arguably this test case is wrong. Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30164
Diffstat (limited to 'gdb/rust-parse.c')
-rw-r--r--gdb/rust-parse.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/gdb/rust-parse.c b/gdb/rust-parse.c
index af1b76f..66263b9 100644
--- a/gdb/rust-parse.c
+++ b/gdb/rust-parse.c
@@ -454,7 +454,7 @@ rust_parser::rust_lookup_type (const char *name)
const struct block *block = pstate->expression_context_block;
munge_name_and_block (&name, &block);
- result = ::lookup_symbol (name, block, SEARCH_STRUCT_DOMAIN, NULL);
+ result = ::lookup_symbol (name, block, SEARCH_TYPE_DOMAIN, nullptr);
if (result.symbol != NULL)
{
update_innermost_block (result);