From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/3] [gdb/symtab] Tweak fix-up of truncated inline function block ranges
Date: Mon, 2 Mar 2026 12:48:46 +0100 [thread overview]
Message-ID: <20260302114849.1797017-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 uses lnp_state_machine::m_last_line in the actual fix.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33930
Tom de Vries (3):
[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] Tweak fix-up of truncated inline function block ranges
gdb/dwarf2/line-program.c | 26 +++++++++++++++++++++-----
1 file changed, 21 insertions(+), 5 deletions(-)
base-commit: bd0babf07de17da6e8e536ceb4dd940d0ed6a0d0
--
2.51.0
next reply other threads:[~2026-03-02 11:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-02 11:48 Tom de Vries [this message]
2026-03-02 11:48 ` [PATCH 1/3] [gdb/symtab] Rename lnp_state_machine::m_last_line to m_last_recorded_line Tom de Vries
2026-03-02 11:48 ` [PATCH 2/3] [gdb/symtab] Re-add lnp_state_machine::m_last_line Tom de Vries
2026-03-02 11:48 ` [PATCH 3/3] [gdb/symtab] Tweak fix-up of truncated inline function block ranges Tom de Vries
2026-03-10 16:05 ` Andrew Burgess
2026-03-10 20:34 ` Tom de Vries
2026-03-14 14:22 ` Andrew Burgess
2026-03-14 14:53 ` Tom de Vries
2026-03-11 13:24 ` Tom de Vries
2026-03-11 15:13 ` Tom de Vries
2026-03-12 6:45 ` Tom de Vries
2026-03-12 12:07 ` Tom de Vries
2026-03-19 15:39 ` Andrew Burgess
2026-04-20 14:38 ` 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=20260302114849.1797017-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