From: Tom de Vries <tdevries@suse.de>
To: Andrew Burgess <aburgess@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb] Fix missing print frame when stepping out of function
Date: Tue, 31 Mar 2026 15:32:35 +0200 [thread overview]
Message-ID: <7b582e85-996f-4052-b6fe-80a85e099eff@suse.de> (raw)
In-Reply-To: <871phh6wir.fsf@redhat.com>
On 3/18/26 3:29 PM, Andrew Burgess wrote:
>> void
>> set_step_info (thread_info *tp, const frame_info_ptr &frame,
>> - struct symtab_and_line sal)
>> + struct symtab_and_line sal, bool refresh_p)
>> {
>> /* This can be removed once this function no longer implicitly relies on the
>> inferior_ptid value. */
>> gdb_assert (inferior_ptid == tp->ptid);
>>
>> + if (refresh_p
>> + && tp->control.step_frame_id != null_frame_id
> Unfortunately, this doesn't work. Comparing frame_ids ends up in
> frame_id::operator== in frame.c, which always returns false if either
> frame-id is null_frame_id. As a result, the != above always returns
> true.
>
I see, thanks for pointing that out.
> I think this is why you ended up having to add the refresh_p argument
> maybe?
To follow up on this (even though we're exploring a different direction
atm), AFAIR I didn't need either of the two things you mention here
(frame comparison and refresh_p) to make the patch work, but I added
them with the intention of making the change more robust.
Thanks,
- Tom
next prev parent reply other threads:[~2026-03-31 13:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-12 12:02 Tom de Vries
2026-03-18 14:29 ` Andrew Burgess
2026-03-19 18:03 ` Tom de Vries
2026-03-31 13:27 ` Tom de Vries
2026-03-31 15:44 ` Andrew Burgess
2026-03-31 13:32 ` Tom de Vries [this message]
2026-04-03 15:17 ` 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=7b582e85-996f-4052-b6fe-80a85e099eff@suse.de \
--to=tdevries@suse.de \
--cc=aburgess@redhat.com \
--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