From: Sergio Durigan Junior <sergiodj@sergiodj.net>
To: Joel Brobecker <brobecker@adacore.com>
Cc: Simon Marchi <simark@simark.ca>,
GDB Patches <gdb-patches@sourceware.org>,
Simon Marchi <simon.marchi@efficios.com>
Subject: Re: [PATCH] gdbserver: Fix build on MIPS
Date: Thu, 16 Jan 2025 11:28:31 -0500 [thread overview]
Message-ID: <87tt9ywwnk.fsf@sergiodj.net> (raw)
In-Reply-To: <Z4iQ1JNlVbDnkQ7O@adacore.com> (Joel Brobecker's message of "Thu, 16 Jan 2025 08:53:40 +0400")
On Wednesday, January 15 2025, Joel Brobecker wrote:
> Hi Sergio,
Hey Joel!
> On Wed, Jan 15, 2025 at 11:07:20PM -0500, Sergio Durigan Junior wrote:
>> On Wednesday, January 15 2025, Simon Marchi wrote:
>>
>> > On 2025-01-15 20:10, Sergio Durigan Junior wrote:
>> >> Commit 3470a0e144df6c01f8479fa649f43aa907936e7e inadvertently broke
>> >> the build on MIPS because it's passing a non-existent "pid" argument
>> >> to "proc->for_each_thread". This commit fixes the problem by removing
>> >> the argument from the call.
>> >>
>> >> Signed-off-by: Sergio Durigan Junior <sergiodj@sergiodj.net>
>> >> ---
>> >> gdbserver/linux-mips-low.cc | 2 +-
>> >> 1 file changed, 1 insertion(+), 1 deletion(-)
>> >>
>> >> diff --git a/gdbserver/linux-mips-low.cc b/gdbserver/linux-mips-low.cc
>> >> index 98733709fa3..fafcdefbb06 100644
>> >> --- a/gdbserver/linux-mips-low.cc
>> >> +++ b/gdbserver/linux-mips-low.cc
>> >> @@ -623,7 +623,7 @@ mips_target::low_remove_point (raw_bkpt_type type, CORE_ADDR addr,
>> >> &priv->watch_mirror);
>> >>
>> >> /* Only update the threads of this process. */
>> >> - proc->for_each_thread (pid, update_watch_registers_callback);
>> >> + proc->for_each_thread (update_watch_registers_callback);
>> >>
>> >> return 0;
>> >> }
>> >
>> > Thanks for catching this.
>> >
>> > Approved-By: Simon Marchi <simon.marchi@efficios.com>
>>
>> Thanks; pushed.
>
> Branch gdb-16-branch also contains
> 3470a0e144df6c01f8479fa649f43aa907936e7e,
> so I'm wondering if it might be worth backporting
> this change to that branch as well?
Yep, I was going to raise this with you but forgot to do that yesterday.
I can do the backport if you want, but I may have forgotten the proper
dance. Do I still need to create a bug?
> (just in time for teh 16.1 release, which is currently
> scheduled for this weekend!)
Great!
Cheers,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
https://sergiodj.net/
next prev parent reply other threads:[~2025-01-16 16:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 1:10 Sergio Durigan Junior
2025-01-16 2:26 ` Simon Marchi
2025-01-16 4:07 ` Sergio Durigan Junior
2025-01-16 4:53 ` Joel Brobecker
2025-01-16 16:28 ` Sergio Durigan Junior [this message]
2025-01-17 2:35 ` Joel Brobecker
2025-01-17 2:50 ` Sergio Durigan Junior
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=87tt9ywwnk.fsf@sergiodj.net \
--to=sergiodj@sergiodj.net \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@efficios.com \
/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