From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v3 0/5] [gdb/tui] Some section hole handling fixes
Date: Mon, 21 Sep 2026 22:55:52 +0200 [thread overview]
Message-ID: <20260921205557.2706300-1-tdevries@suse.de> (raw)
This series consists of 5 patches.
The first three patches are refactoring/infrastructure patches:
- factor out update_section_map
- add section_addrmap
- extend addrmap::find with low/high results
The fourth patch fixes PR34617, for both TUI and CLI.
The fifth patch prevents stopping disassembly at section holes for CLI
and TUI, fixing PR34399.
Changes in v2:
- add patch fixing tui_disassemble comment after review comment
- drop restrictive fix for PR tui/34399 after review comments
- add patches implementing an enabling fix for PR tui/34399.
Changes in v3:
- committed the first three patches of v2
- drop the find_pc_section refactoring approach of the 4th and 5th patches of
v2
- instead add three refactoring/infrastructure patches:
- factor out update_section_map
- add section_addrmap
- extend addrmap::find with low/high results
- rework the last two patches into these two patches:
- handle sections when disassembling
- don't stop disassembly at section hole
Versions:
- v1 https://sourceware.org/pipermail/gdb-patches/2026-August/229584.html
- v2 https://sourceware.org/pipermail/gdb-patches/2026-September/230207.html
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34399
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=34617
Tom de Vries (5):
[gdb] Factor out update_section_map
[gdb] Add section_addrmap
[gdb] Extend addrmap::find with low/high results
[gdb] Handle sections when disassembling
[gdb] Don't stop disassembly at section hole
gdb/addrmap.c | 78 ++++++++++++++++++++++++---
gdb/addrmap.h | 23 +++++---
gdb/disasm.c | 123 ++++++++++++++++++++++++++++++++++++++-----
gdb/disasm.h | 14 +++++
gdb/objfiles.c | 62 +++++++++++++++++-----
gdb/objfiles.h | 6 +++
gdb/tui/tui-disasm.c | 120 ++++++++++++++++++++++++++++++-----------
7 files changed, 356 insertions(+), 70 deletions(-)
base-commit: 3e5100fe3b15e2b3ece60f57b4c1ecc0c50cae53
--
2.51.0
next reply other threads:[~2026-09-21 20:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 20:55 Tom de Vries [this message]
2026-09-21 20:55 ` [PATCH v3 1/5] [gdb] Factor out update_section_map Tom de Vries
2026-09-21 20:55 ` [PATCH v3 2/5] [gdb] Add section_addrmap Tom de Vries
2026-09-21 20:55 ` [PATCH v3 3/5] [gdb] Extend addrmap::find with low/high results Tom de Vries
2026-09-21 20:55 ` [PATCH v3 4/5] [gdb] Handle sections when disassembling Tom de Vries
2026-09-21 20:55 ` [PATCH v3 5/5] [gdb] Don't stop disassembly at section hole 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=20260921205557.2706300-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