From: Guinevere Larsen <blarsen@redhat.com>
To: Sahil <icegambit91@gmail.com>, gdb-patches@sourceware.org
Cc: Sahil Siddiq <sahilcdq@proton.me>,
"Eli Zaretskii (eliz@gnu.org)" <eliz@gnu.org>
Subject: Re: [PATCH v3] gdb: fix "frame function" failure to get frame when call is it's last instruction
Date: Fri, 5 Jul 2024 11:38:11 -0300 [thread overview]
Message-ID: <6436e55a-eedd-4c15-9ea1-693cf3680cee@redhat.com> (raw)
In-Reply-To: <4933009.GXAFRqVoOG@valdaarhun>
On 7/5/24 11:23 AM, Sahil wrote:
> Hi,
>
> Thank you for the review.
>
> On Friday, July 5, 2024 6:36:52 PM GMT+5:30 Guinevere Larsen wrote:
>> [...]
>> I have tested, it fixes the issue reported and adds no regressions! I
>> have a minor nit inlined, but with that fixes, feel free to add my git
>> trailer to the commit message:
>>
>> Reviewed-By: Guinevere Larsen <blarsen@redhat.com>
>>
>> I hope a maintainer approves this for pushing soon!
>>
>> [...]
>>> diff --git a/gdb/testsuite/gdb.base/frame-selection.exp
>>> b/gdb/testsuite/gdb.base/frame-selection.exp index e8d9c87c3a..4333f6a2d1
>>> 100644
>>> --- a/gdb/testsuite/gdb.base/frame-selection.exp
>>> +++ b/gdb/testsuite/gdb.base/frame-selection.exp
>>> @@ -63,7 +63,7 @@ proc check_frame { level address function } {
>>>
>>> set re [multi_line \
>>>
>>> "Stack level ${level}, frame at ($address):" \
>>>
>>> - ".* = $hex in ${function} \(\[^\r\n\]*\); saved .* = $hex" \
>>> + ".* = $hex in ${function}( \(\[^\r\n\]*\))*; saved .* = $hex" \
>> This looks like a spurious change. I removed the change and everything
>> works.
>>
>> There's no need to send a new version for just this change though, just
>> fix it locally and apply my review tag :)
>>
> Since this is my first time contributing to gdb, I am a little unsure
> about what comes next.
>
> My understanding is that a maintainer will respond to this thread
> with an "Approved-By" tag and then I'll be able to push this patch
> to the repository with the "Reviewed-By" and "Approved-By" tags
> appended in the commit message. Is this correct?
>
> Thanks,
> Sahil
>
>
If you have completed the copyright assignment process, yes that's
exactly it. If you haven't, you'll need that finished before being
allowed to push, since I think the changes to the testcase would be
considered legally significant.
I'm not sure if you should start the assignment process yet, since the
patch hasn't been approved. Eli (CC'd because of this question), should
Sahil start the assignment process already, or wait for someone to
approve their patch first?
--
Cheers,
Guinevere Larsen
She/Her/Hers
next prev parent reply other threads:[~2024-07-05 14:38 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 [this message]
2024-07-05 18:16 ` Eli Zaretskii
2024-07-06 8:44 ` Sahil
2025-10-22 17:50 ` Tom Tromey
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=6436e55a-eedd-4c15-9ea1-693cf3680cee@redhat.com \
--to=blarsen@redhat.com \
--cc=eliz@gnu.org \
--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