From: Tom Tromey <tom@tromey.com>
To: Sahil Siddiq <icegambit91@gmail.com>
Cc: gdb-patches@sourceware.org, Sahil Siddiq <sahilcdq@proton.me>
Subject: Re: [PATCH v3] gdb: fix "frame function" failure to get frame when call is it's last instruction
Date: Wed, 22 Oct 2025 11:50:39 -0600 [thread overview]
Message-ID: <87v7k6keq8.fsf@tromey.com> (raw)
In-Reply-To: <20240704163348.67304-1-sahilcdq@proton.me> (Sahil Siddiq's message of "Thu, 4 Jul 2024 22:03:48 +0530")
>>>>> Sahil Siddiq <icegambit91@gmail.com> writes:
> "frame function" currently fails to retrieve the frame
> associated with a function when the last instruction
> in the frame is a call. This is because the instruction
> pointer points to an address that lies outside the frame.
> Using "get_frame_address_in_block" instead of "get_frame_pc"
> resolves this issue.
I ran across this patch... whatever happened here?
Did you get a copyright assignment sorted out?
thanks,
Tom
prev parent reply other threads:[~2025-10-22 17:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 16:33 Sahil Siddiq
2024-07-05 13:06 ` Guinevere Larsen
2024-07-05 14:23 ` Sahil
2024-07-05 14:38 ` Guinevere Larsen
2024-07-05 18:16 ` Eli Zaretskii
2024-07-06 8:44 ` Sahil
2025-10-22 17:50 ` Tom Tromey [this message]
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=87v7k6keq8.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=icegambit91@gmail.com \
--cc=sahilcdq@proton.me \
/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