From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/tui] Fix gdb.tui/tui-layout-asm-short-prog.exp
Date: Sat, 19 Sep 2026 23:37:57 +0200 [thread overview]
Message-ID: <20260919213757.3097642-1-tdevries@suse.de> (raw)
Recent commit ("[gdb/tui] Improve section handling in
tui_find_backward_disassembly_start_address") breaks test-case
gdb.tui/tui-layout-asm-short-prog.exp on aarch64-linux, because it expects not
being able to disassemble instructions before .text.
It's easy enough to fix that using:
...
-Term::command "- 15"
+Term::command "- 4"
...
but AFAIU, that breaks the purpose of the test-case.
So instead, used objcopy --remove-section=.note.* to strip the sections
before .text.
---
gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.exp | 12 ++++++++++++
1 file changed, 12 insertions(+)
diff --git a/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.exp b/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.exp
index b3dd72ce1ce..6a668ad16d0 100644
--- a/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.exp
+++ b/gdb/testsuite/gdb.tui/tui-layout-asm-short-prog.exp
@@ -30,6 +30,18 @@ if { [build_executable "failed to prepare" $testfile $srcfile $opts] == -1 } {
return
}
+# This test-case relies on not being able to scroll to before _start. Strip
+# the notes to make sure there are no sections before start.
+
+set objcopy_program [gdb_find_objcopy]
+set res \
+ [remote_exec host \
+ "$objcopy_program --remove-section=.note.* $binfile"]
+if {[lindex $res 0] != 0} {
+ unsupported "Couldn't strip notes"
+ return
+}
+
Term::clean_restart 24 80 $testfile
if {![Term::prepare_for_tui]} {
unsupported "TUI not supported"
base-commit: e26e14a40e9be83fa37a2c42be93404415facf80
--
2.51.0
reply other threads:[~2026-09-19 21:38 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=20260919213757.3097642-1-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