public inbox for
 help / color / mirror / Atom feed
From: Nick <>
To: "Dmitry V. Levin" <>,
Subject: Re: elfutils does not compile with gcc 12.2.0
Date: Thu, 25 Aug 2022 10:51:10 +0200	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 8/24/22 23:01, Dmitry V. Levin wrote:

> On Wed, Aug 24, 2022 at 10:51:13PM +0200, Nick via Elfutils-devel wrote:
>> I try to compile elfutils on OpenWrt with the newest gcc 12.2.0 version.
>> However, it fails due to -Werror=use-after-free. A workaround is a patch
>> that I found on the mailinglist, to disable -Werror
>> (
>> I modified it to apply to newest elfutils version. The error with
>> elfutils 0.187 and gcc 12.2.0:
>> In function 'bigger_buffer',
>>       inlined from '__libdw_gunzip' at gzip.c:376:12:
>> gzip.c:98:9: error: pointer may be used after 'realloc'
>> [-Werror=use-after-free]
>>      98 |     b = realloc (state->buffer, more -= 1024);
>>         |         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> gzip.c:96:13: note: call to 'realloc' here
>>      96 |   char *b = realloc (state->buffer, more);
>>         |             ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> This warning is definitely wrong, looks like a regression in gcc, please
> report this to compiler people, otherwise they will never know they
> introduced a bug that needs fixing.
I think it is not the only failure. I added a comment under this already 
existing bug report:

If you look at this comment I am not sure if that is ever fixed:
The write here about using "pragma" statements to suppress the warning.
What about introducing the disabling of werror by a configure flag?


      reply	other threads:[~2022-08-25  8:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-24 20:51 Nick
2022-08-24 21:01 ` Dmitry V. Levin
2022-08-25  8:51   ` Nick [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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).