Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [RFC v2 0/3] [gdb] Fix missing print frame when stepping out of function
Date: Tue, 31 Mar 2026 15:23:39 +0200	[thread overview]
Message-ID: <20260331132342.1050954-1-tdevries@suse.de> (raw)

This patch series consisting of three patches.

The first two patches do some refactoring, to make the last patch minimal.

The last patch contains a fix for PR33981 (though it introduces a new problem,
hence the RFC).

A v1 was submitted here [1].

Changes in v2:
- added two refactoring patches
- changed approach after review comment by Andrew, changing
  in_step_start_function usage to notice stepping in and out of inlined
  functions

Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=33981

[1] https://sourceware.org/pipermail/gdb-patches/2026-March/225916.html

Tom de Vries (3):
  [gdb/symtab] Add find_symbol_for_pc_maybe_inline
  [gdb] Add thread_control_state::step_start_function methods
  [gdb] Fix missing print frame when stepping out of function

 gdb/blockframe.c                              |  8 ++++
 gdb/gdbthread.h                               | 41 ++++++++++++++++-
 gdb/infcmd.c                                  |  5 +--
 gdb/infrun.c                                  | 12 +++--
 gdb/symtab.h                                  |  6 +++
 .../gdb.dwarf2/dw2-extend-inline-block.exp    | 45 +++++++++++++++++--
 6 files changed, 102 insertions(+), 15 deletions(-)


base-commit: ad6615bf96d148a238f21907caebf8100f92d74e
-- 
2.51.0


             reply	other threads:[~2026-03-31 13:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 13:23 Tom de Vries [this message]
2026-03-31 13:23 ` [RFC v2 1/3] [gdb/symtab] Add find_symbol_for_pc_maybe_inline Tom de Vries
2026-03-31 13:23 ` [RFC v2 2/3] [gdb] Add thread_control_state::step_start_function methods Tom de Vries
2026-03-31 13:23 ` [RFC v2 3/3] [gdb] Fix missing print frame when stepping out of function Tom de Vries
2026-04-05 10:12 ` [PATCH 0/2] " Andrew Burgess
2026-04-05 10:12   ` [PATCH 1/2] gdb: use get_current_frame consistently in print_stop_location Andrew Burgess
2026-04-09  6:42     ` Tom de Vries
2026-04-09  8:54       ` Andrew Burgess
2026-04-09 13:43         ` Tom de Vries
2026-04-10  8:57           ` Andrew Burgess
2026-04-10 10:17             ` Tom de Vries
2026-04-05 10:12   ` [PATCH 2/2] gdb: fix missing print frame when stepping out of function Andrew Burgess
2026-04-10 10:29     ` Tom de Vries
2026-04-10 10:48   ` [PATCH 0/2] Fix " 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=20260331132342.1050954-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