public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "vvinayag at arm dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug build/26779] benign use after realloc at localealias.c:329
Date: Wed, 09 Feb 2022 14:05:17 +0000 [thread overview]
Message-ID: <bug-26779-131-6Rje3rTduO@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-26779-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=26779
vvinayag at arm dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |vvinayag at arm dot com
--- Comment #8 from vvinayag at arm dot com ---
(In reply to Martin Sebor from comment #7)
> Fixed by the changes below:
>
> https://sourceware.org/pipermail/glibc-cvs/2022q1/076319.html
> https://sourceware.org/pipermail/glibc-cvs/2022q1/076320.html
> https://sourceware.org/pipermail/glibc-cvs/2022q1/076321.html
> https://sourceware.org/pipermail/glibc-cvs/2022q1/076322.html
> https://sourceware.org/pipermail/glibc-cvs/2022q1/076324.html
Hi,
I am still seeing this error when building on aarch64-none-linux-gnu with
bootstrapping glibc.
Build = Host = Target = aarch64-none-linux-gnu
or
Build = Host = Target = arm-none-linux-gnueabihf
localealias.c: In function 'read_alias_file':
localealias.c:335:56: error: pointer may be used after 'realloc'
[-Werror=use-after-free]
335 | map[i].alias += new_pool - string_space;
| ~~~~~~~~~^~~~~~~~~~~~~~
localealias.c:325:49: note: call to 'realloc' here
325 | char *new_pool = (char *) realloc (string_space,
new_size);
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
localealias.c: In function 'read_alias_file':
localealias.c:335:56: error: pointer may be used after 'realloc'
[-Werror=use-after-free]
335 | map[i].alias += new_pool - string_space;
| ~~~~~~~~~^~~~~~~~~~~~~~
localealias.c:325:49: note: call to 'realloc' here
325 | char *new_pool = (char *) realloc (string_space,
new_size);
|
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2022-02-09 14:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 17:12 [Bug build/26779] New: " msebor at gmail dot com
2020-10-23 21:14 ` [Bug build/26779] " msebor at gmail dot com
2020-10-27 21:21 ` msebor at gmail dot com
2020-10-27 21:41 ` msebor at gmail dot com
2022-01-12 17:16 ` msebor at gmail dot com
2022-01-12 17:20 ` msebor at gmail dot com
2022-01-14 0:28 ` msebor at gmail dot com
2022-01-26 17:43 ` msebor at gmail dot com
2022-01-26 20:24 ` carlos at redhat dot com
2022-02-09 14:05 ` vvinayag at arm dot com [this message]
2022-02-09 14:59 ` schwab@linux-m68k.org
2022-02-09 16:13 ` vvinayag at arm dot com
2024-01-11 9:33 ` fweimer at redhat dot com
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=bug-26779-131-6Rje3rTduO@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).