From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH v2 0/5] [gdb/symtab] Tweak fix-up of truncated inline function block ranges
Date: Mon, 20 Apr 2026 15:46:03 +0200 [thread overview]
Message-ID: <20260420134608.2537059-1-tdevries@suse.de> (raw)
This patch series fixes PR33930, a FAIL in test-case
gdb.cp/step-and-next-inline.exp on ppc64le-linux.
The first patch is a simple refactoring patch, renaming
lnp_state_machine::m_last_line (tracking the last recorded line) to the more
accurate m_last_recorded_line.
The second patch reintroduces lnp_state_machine::m_last_line, with semantics
matching the name (tracking all lines, not just recorded ones).
The third patch is another refactoring patch, simplifying the conditional
assignment of lnp_state_machine::m_last_address.
The fourth patch is yet another refactoring patch, adding
lnp_state_machine::m_stmt_at_last_address.
The fifth patch uses lnp_state_machine::m_last_line in the actual fix.
A v1 was submitted here [1].
Changes in v2:
- add a refactoring patch, simplifying the conditional assignment of
lnp_state_machine::m_last_address
- add a refactoring patch, adding lnp_state_machine::m_stmt_at_last_address
- remove workaround in gdb.dwarf2/dw2-extend-inline-block.exp
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33930
[1] v1 https://sourceware.org/pipermail/gdb-patches/2026-March/225480.html
Tom de Vries (5):
[gdb/symtab] Rename lnp_state_machine::m_last_line to
m_last_recorded_line
[gdb/symtab] Re-add lnp_state_machine::m_last_line
[gdb/symtab] Simplify assignment in lnp_state_machine::record_line
[gdb/symtab] Add lnp_state_machine::m_stmt_at_last_address
[gdb/symtab] Tweak fix-up of truncated inline function block ranges
gdb/dwarf2/line-program.c | 52 ++++++++++++-------
.../gdb.dwarf2/dw2-extend-inline-block.exp | 5 --
2 files changed, 34 insertions(+), 23 deletions(-)
base-commit: 971b0152e92d381917bb089b3783959c5feb552e
--
2.51.0
next reply other threads:[~2026-04-20 13:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-20 13:46 Tom de Vries [this message]
2026-04-20 13:46 ` [PATCH v2 1/5] [gdb/symtab] Rename lnp_state_machine::m_last_line to m_last_recorded_line Tom de Vries
2026-04-20 13:46 ` [PATCH v2 2/5] [gdb/symtab] Re-add lnp_state_machine::m_last_line Tom de Vries
2026-04-20 13:46 ` [PATCH v2 3/5] [gdb/symtab] Simplify assignment in lnp_state_machine::record_line Tom de Vries
2026-04-20 13:46 ` [PATCH v2 4/5] [gdb/symtab] Add lnp_state_machine::m_stmt_at_last_address Tom de Vries
2026-04-20 13:46 ` [PATCH v2 5/5] [gdb/symtab] Tweak fix-up of truncated inline function block ranges Tom de Vries
2026-07-29 11:01 ` [PING][PATCH v2 0/5] " 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=20260420134608.2537059-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