Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Lancelot SIX <lsix@lancelotsix.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/build] Fix unused var in corelow.c
Date: Tue, 10 Sep 2024 10:09:09 +0200	[thread overview]
Message-ID: <2a9b49f3-0242-4319-98a2-f78d02f52332@suse.de> (raw)
In-Reply-To: <mbdup2v6rjvvs34jhpmjn5gkwuqlou2c5pqginul6rvecitwn6@jw6mv4udaiu2>

On 9/9/24 15:35, Lancelot SIX wrote:
> Hi,
> 
> FYI, I see the same issue on a CI system.
> 
> FWIW, the patch looks good to me.
> 

Hi Lancelot,

thanks for the review, pushed.

- Tom

> Reviewed-By: Lancelot Six<lancelot.six@amd.com>
> 
> Best,
> Lancelot.
> 
> On Mon, Sep 09, 2024 at 06:19:13AM +0200, Tom de Vries wrote:
>> On x86_64-linux, with gcc 7.5.0 and CFLAGS/CXXFLAGS="-O0 -g -Wall" I ran into
>> a build breaker:
>> ...
>> gdb/corelow.c: In member function ‘void mapped_file_info::add(const char*, const char*, const char*, std::vector<mem_range>&&, const bfd_build_id*)’:
>> gdb/corelow.c:1822:27: error: unused variable ‘it’ [-Werror=unused-variable]
>>     const auto [it, inserted]
>>                             ^
>> ...
>>
>> Fix this by dropping the variable it.
>>
>> Tested on x86_64-linux.
>> ---
>>   gdb/corelow.c | 4 ++--
>>   1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/gdb/corelow.c b/gdb/corelow.c
>> index 16f07c23faa..ab2fa746de8 100644
>> --- a/gdb/corelow.c
>> +++ b/gdb/corelow.c
>> @@ -1819,8 +1819,8 @@ mapped_file_info::add (const char *soname,
>>        parsed, we group the build-id information based on the file name.  As
>>        a consequence, we should see each EXPECTED_FILENAME value exactly
>>        once.  This means that each insertion should always succeed.  */
>> -  const auto [it, inserted]
>> -    = m_filename_to_build_id_map.emplace (expected_filename, build_id);
>> +  const auto inserted
>> +    = m_filename_to_build_id_map.emplace (expected_filename, build_id).second;
>>     gdb_assert (inserted);
>>   
>>     /* Setup the reverse build-id to file name map.  */
>>
>> base-commit: 29c70787112e01cd52b53bf14bdcacb0a11e0725
>> -- 
>> 2.35.3
>>


      reply	other threads:[~2024-09-10  8:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09  4:19 Tom de Vries
2024-09-09 13:35 ` Lancelot SIX
2024-09-10  8:09   ` Tom de Vries [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=2a9b49f3-0242-4319-98a2-f78d02f52332@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=lsix@lancelotsix.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