From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v4 02/11] [gdb/tui] Make low_prev loop-local in tui_find_disassembly_address
Date: Wed, 7 Oct 2026 11:40:48 +0200 [thread overview]
Message-ID: <20261007094057.1811886-3-tdevries@suse.de> (raw)
In-Reply-To: <20261007094057.1811886-1-tdevries@suse.de>
There's a loop in tui_find_disassembly_address:
...
CORE_ADDR prev_low;
...
do
{
...
if (last_addr >= pc && new_low != prev_low
&& asm_lines.size () >= max_lines)
...
}
while ((last_addr > pc
|| (last_addr == pc && asm_lines.size () < max_lines))
&& new_low != prev_low);
...
Simplify the two conditions by handling new_low == prev_low before:
...
if (new_low == prev_low)
break;
...
Now that prev_low is no longer tested in the loop condition, make it a
loop-local variable.
No functional changes.
---
gdb/tui/tui-disasm.c | 20 ++++++++++----------
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/gdb/tui/tui-disasm.c b/gdb/tui/tui-disasm.c
index e9f5969a6e6..18439580ffb 100644
--- a/gdb/tui/tui-disasm.c
+++ b/gdb/tui/tui-disasm.c
@@ -234,15 +234,14 @@ tui_find_disassembly_address (struct gdbarch *gdbarch, CORE_ADDR pc, int from)
will fall back to the address held here. */
std::optional<CORE_ADDR> possible_new_low;
- /* The previous value of NEW_LOW so we know if the new value is
- different or not. */
- CORE_ADDR prev_low;
-
CORE_ADDR new_low = pc;
do
{
+ /* The previous value of NEW_LOW so we know if the new value is
+ different or not. */
+ CORE_ADDR prev_low = new_low;
+
/* Find an address from which we can start disassembling. */
- prev_low = new_low;
new_low = tui_find_backward_disassembly_start_address (new_low);
/* Disassemble forward. */
@@ -251,11 +250,13 @@ tui_find_disassembly_address (struct gdbarch *gdbarch, CORE_ADDR pc, int from)
break;
last_addr = asm_lines.back ().addr;
+ if (new_low == prev_low)
+ break;
+
/* If disassembling from the current value of NEW_LOW reached PC
(or went past it) then this would do as a starting point if we
can't find anything better, so remember it. */
- if (last_addr >= pc && new_low != prev_low
- && asm_lines.size () >= max_lines)
+ if (last_addr >= pc && asm_lines.size () >= max_lines)
possible_new_low.emplace (new_low);
/* Continue searching until we find a value of NEW_LOW from which
@@ -263,9 +264,8 @@ tui_find_disassembly_address (struct gdbarch *gdbarch, CORE_ADDR pc, int from)
know this means we can find the required number of previous
instructions then. */
}
- while ((last_addr > pc
- || (last_addr == pc && asm_lines.size () < max_lines))
- && new_low != prev_low);
+ while (last_addr > pc
+ || (last_addr == pc && asm_lines.size () < max_lines));
/* If we failed to disassemble the required number of lines, try to fall
back to a previous possible start address in POSSIBLE_NEW_LOW. */
--
2.51.0
next prev parent reply other threads:[~2026-10-07 9:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-07 9:40 [PATCH v4 00/11] [gdb/tui] Some section hole handling fixes Tom de Vries
2026-10-07 9:40 ` [PATCH v4 01/11] [gdb/tui] Use early exit in tui_find_disassembly_address Tom de Vries
2026-10-07 9:40 ` Tom de Vries [this message]
2026-10-07 9:40 ` [PATCH v4 03/11] [gdb/tui] Disassemble less often " Tom de Vries
2026-10-07 9:40 ` [PATCH v4 04/11] [gdb/tui] Fix buglet " Tom de Vries
2026-10-07 9:40 ` [PATCH v4 05/11] [gdb] Factor out update_section_map Tom de Vries
2026-10-07 9:40 ` [PATCH v4 06/11] [gdb] Add section_addrmap Tom de Vries
2026-10-07 9:40 ` [PATCH v4 07/11] [gdb] Extend addrmap::find with low/high results Tom de Vries
2026-10-07 9:40 ` [PATCH v4 08/11] [gdb] Make gdb_disassembly return number of insns Tom de Vries
2026-10-07 9:40 ` [PATCH v4 09/11] [gdb] Handle sections when disassembling Tom de Vries
2026-10-07 9:40 ` [PATCH v4 10/11] [gdb] Don't stop disassembly at section hole Tom de Vries
2026-10-07 9:40 ` [PATCH v4 11/11] [RFC, gdb/tui] Don't scroll into non-code sections 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=20261007094057.1811886-3-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