public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "siddhesh at gotplt dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88783] integer overflow in libiberty, heap overflow will be triggered in nm
Date: Wed, 24 Feb 2021 04:30:31 +0000 [thread overview]
Message-ID: <bug-88783-4-QPLBvd8tVB@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88783-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88783
Siddhesh Poyarekar <siddhesh at gotplt dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |siddhesh at gotplt dot org
--- Comment #9 from Siddhesh Poyarekar <siddhesh at gotplt dot org> ---
gcc version of libiberty hasn't had this issue since the following change which
removed the potential overflow. The POC also appears fixed with binutils 2.35;
from code inspection it should be fixed in 2.32 and later. This ought to be
closed.
ommit 6c8120c5ff130e03d32ff15a8f0d0e703592a2af
Author: Jason Merrill <jason@redhat.com>
Date: Sat Dec 22 19:06:34 2018 -0500
Remove support for demangling GCC 2.x era mangling schemes.
libiberty/
* cplus-dem.c: Remove cplus_mangle_opname, cplus_demangle_opname,
internal_cplus_demangle, and all subroutines.
(libiberty_demanglers): Remove entries for ancient GNU (pre-3.0),
Lucid, ARM, HP, and EDG demangling styles.
(cplus_demangle): Remove 'work' variable. Don't call
internal_cplus_demangle.
include/
* demangle.h: Remove support for ancient GNU (pre-3.0), Lucid,
ARM, HP, and EDG demangling styles.
From-SVN: r267363
prev parent reply other threads:[~2021-02-24 4:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88783-4@http.gcc.gnu.org/bugzilla/>
2020-05-07 12:17 ` trupti_pardeshi at persistent dot co.in
2021-01-12 7:42 ` prajwapa at in dot ibm.com
2021-01-13 8:56 ` prajwapa at in dot ibm.com
2021-02-24 4:30 ` siddhesh at gotplt dot org [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=bug-88783-4-QPLBvd8tVB@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).