public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 2/2] [gdb/tui] Only handle code sections in tui_find_backward_disassembly_start_address
Date: Tue,  5 Sep 2023 17:03:39 +0200	[thread overview]
Message-ID: <20230905150339.6452-2-tdevries@suse.de> (raw)
In-Reply-To: <20230905150339.6452-1-tdevries@suse.de>

After adding a unit test in gdb/tui/tui-disasm.c excercising
tui_find_disassembly_address, I decided to try to extend it using addresses
around section borders.

The new test was very slow (when using gdb as inferior, as is done in
gdb.gdb/unittest.exp), due to disassembling entire non-code sections.

Fix this this by limiting tui_find_backward_disassembly_start_address to
SEC_CODE sections.

FWIW, compared to other self-tests it's still somewhat slow:
...
(gdb) maint selftest
  ...
Command execution time: 1.535391 (cpu), 1.571246 (wall)
(gdb) maint selftest tui-disasm
  ...
Command execution time: 0.482022 (cpu), 0.482028 (wall)
...
This is for calling gdb_print_insn ~550 times.

Tested on x86_64-linux.
---
 gdb/tui/tui-disasm.c | 50 +++++++++++++++++++++++++++++++++++++-------
 1 file changed, 43 insertions(+), 7 deletions(-)

diff --git a/gdb/tui/tui-disasm.c b/gdb/tui/tui-disasm.c
index 03c78aa1291..c31ab5b0680 100644
--- a/gdb/tui/tui-disasm.c
+++ b/gdb/tui/tui-disasm.c
@@ -46,6 +46,8 @@
 
 #include "gdb_curses.h"
 
+#include <unordered_set>
+
 struct tui_asm_line
 {
   CORE_ADDR addr;
@@ -164,6 +166,15 @@ tui_disassemble (struct gdbarch *gdbarch,
 static CORE_ADDR
 tui_find_backward_disassembly_start_address (CORE_ADDR addr)
 {
+  struct obj_section *section = find_pc_section (addr);
+  /* Don't handle addresses not in a known section.  */
+  if (section == nullptr)
+    return addr;
+
+  /* Only handle sections with only code.  */
+  if ((section->the_bfd_section->flags & SEC_CODE) == 0)
+    return addr;
+
   struct bound_minimal_symbol msym, msym_prev;
 
   msym = lookup_minimal_symbol_by_pc_section (addr - 1, nullptr,
@@ -174,13 +185,8 @@ tui_find_backward_disassembly_start_address (CORE_ADDR addr)
   else if (msym_prev.minsym != nullptr)
     return msym_prev.value_address ();
 
-  /* Find the section that ADDR is in, and look for the start of the
-     section.  */
-  struct obj_section *section = find_pc_section (addr);
-  if (section != NULL)
-    return section->addr ();
-
-  return addr;
+  /* Use the start of the section.  */
+  return section->addr ();
 }
 
 /* Find the disassembly address that corresponds to FROM lines above
@@ -545,6 +551,36 @@ run_tests ()
 	 being passed a PC for which gdb_print_insn throws a MEMORY_ERROR.  */
       SELF_CHECK (tui_find_disassembly_address (gdbarch, 0, 1) == 0);
       SELF_CHECK (tui_find_disassembly_address (gdbarch, 0, -1) == 0);
+
+      /* Poke around the edges of sections.  */
+      gdbarch_iterate_over_objfiles_in_search_order
+	(target_gdbarch (),
+	 [gdbarch] (objfile *obj)
+	 {
+	   std::unordered_set<CORE_ADDR> visited;
+
+	   /* Already done above.  */
+	   visited.insert (0);
+
+	   for (obj_section *osect : obj->sections ())
+	     {
+	       CORE_ADDR first_addr = osect->addr ();
+	       CORE_ADDR last_addr = osect->endaddr () - 1;
+
+	       for (auto addr_ : { first_addr, last_addr })
+		 for (int offset = -1; offset <= 1; ++offset)
+		   {
+		     CORE_ADDR addr = addr_ + offset;
+		     if (visited.find (addr) != visited.end ())
+		       continue;
+
+		     tui_find_disassembly_address (gdbarch, addr, 1);
+		     tui_find_disassembly_address (gdbarch, addr, -1);
+		     visited.insert (addr);
+		   }
+	     }
+	   return false;
+	 }, nullptr);
     }
 }
 
-- 
2.35.3


  reply	other threads:[~2023-09-05 15:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-05 15:03 [PATCH 1/2] [gdb/tui] Fix segfault in tui_find_disassembly_address Tom de Vries
2023-09-05 15:03 ` Tom de Vries [this message]
2023-09-27 16:15   ` [PATCH 2/2] [gdb/tui] Only handle code sections in tui_find_backward_disassembly_start_address Kevin Buettner
2023-09-28 18:23     ` Tom de Vries
2023-09-26 15:22 ` [PING][PATCH 1/2] [gdb/tui] Fix segfault in tui_find_disassembly_address Tom de Vries
2023-09-27 16:10 ` [PATCH " Kevin Buettner
2023-09-28 20:57   ` Tom de Vries
2023-09-29 10:08     ` Tom de Vries

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=20230905150339.6452-2-tdevries@suse.de \
    --to=tdevries@suse.de \
    --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).