From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [pushed] Remove expand_symtab_containing_pc
Date: Sun, 26 Feb 2023 10:52:36 -0700 [thread overview]
Message-ID: <20230226175236.2206328-1-tom@tromey.com> (raw)
The function expand_symtab_containing_pc is unused; remove it.
Tested by rebuilding.
---
gdb/symtab.c | 23 -----------------------
gdb/symtab.h | 4 ----
2 files changed, 27 deletions(-)
diff --git a/gdb/symtab.c b/gdb/symtab.c
index 25b55ed01e7..f26dd2cb187 100644
--- a/gdb/symtab.c
+++ b/gdb/symtab.c
@@ -1162,29 +1162,6 @@ matching_obj_sections (struct obj_section *obj_first,
return false;
}
-
-/* See symtab.h. */
-
-void
-expand_symtab_containing_pc (CORE_ADDR pc, struct obj_section *section)
-{
- struct bound_minimal_symbol msymbol;
-
- /* If we know that this is not a text address, return failure. This is
- necessary because we loop based on texthigh and textlow, which do
- not include the data ranges. */
- msymbol = lookup_minimal_symbol_by_pc_section (pc, section);
- if (msymbol.minsym && msymbol.minsym->data_p ())
- return;
-
- for (objfile *objfile : current_program_space->objfiles ())
- {
- struct compunit_symtab *cust
- = objfile->find_pc_sect_compunit_symtab (msymbol, pc, section, 0);
- if (cust)
- return;
- }
-}
\f
/* Hash function for the symbol cache. */
diff --git a/gdb/symtab.h b/gdb/symtab.h
index 17d2746fd48..c565bc8eac4 100644
--- a/gdb/symtab.h
+++ b/gdb/symtab.h
@@ -2189,10 +2189,6 @@ extern bound_minimal_symbol find_gnu_ifunc (const symbol *sym);
extern void clear_pc_function_cache (void);
-/* Expand symtab containing PC, SECTION if not already expanded. */
-
-extern void expand_symtab_containing_pc (CORE_ADDR, struct obj_section *);
-
/* lookup full symbol table by address. */
extern struct compunit_symtab *find_pc_compunit_symtab (CORE_ADDR);
--
2.39.1
reply other threads:[~2023-02-26 17:52 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=20230226175236.2206328-1-tom@tromey.com \
--to=tom@tromey.com \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).