From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 2/5] Remove unnecessary null check in lookup_minimal_symbol_by_pc_section
Date: Tue, 28 May 2024 13:23:55 -0600 [thread overview]
Message-ID: <20240528-dwarf-race-relocate-v2-2-a8d042e75925@tromey.com> (raw)
In-Reply-To: <20240528-dwarf-race-relocate-v2-0-a8d042e75925@tromey.com>
lookup_minimal_symbol_by_pc_section asserts that section != NULL early
in the function, rendering a later check (and comment) unnecessary.
---
gdb/minsyms.c | 8 +++-----
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git a/gdb/minsyms.c b/gdb/minsyms.c
index ea557d3625f..97b1a1c15c8 100644
--- a/gdb/minsyms.c
+++ b/gdb/minsyms.c
@@ -875,13 +875,11 @@ lookup_minimal_symbol_by_pc_section (CORE_ADDR pc_in, struct obj_section *sectio
continue;
}
- /* If SECTION was specified, skip any symbol from
- wrong section. */
- if (section
- /* Some types of debug info, such as COFF,
+ /* Skip any symbol from wrong section. */
+ if (/* Some types of debug info, such as COFF,
don't fill the bfd_section member, so don't
throw away symbols on those platforms. */
- && msymbol[hi].obj_section (objfile) != nullptr
+ msymbol[hi].obj_section (objfile) != nullptr
&& (!matching_obj_sections
(msymbol[hi].obj_section (objfile),
section)))
--
2.44.0
next prev parent reply other threads:[~2024-05-28 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 19:23 [PATCH v2 0/5] Cleanups " Tom Tromey
2024-05-28 19:23 ` [PATCH v2 1/5] Compare section index " Tom Tromey
2024-05-28 19:23 ` Tom Tromey [this message]
2024-05-28 19:23 ` [PATCH v2 3/5] Hoist a call to frob_address Tom Tromey
2024-05-28 19:23 ` [PATCH v2 4/5] Use bound_minimal_symbol more in lookup_minimal_symbol_by_pc_section Tom Tromey
2024-05-28 19:23 ` [PATCH v2 5/5] Fix address comparison " 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=20240528-dwarf-race-relocate-v2-2-a8d042e75925@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).