public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "nickc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug demangler/88629] Regression lead to Heap-buffer-overflow problem in function d_expression_1 in cp-demangle.c, as demonstrated by c++filt
Date: Tue, 12 Jan 2021 11:23:41 +0000 [thread overview]
Message-ID: <bug-88629-4-qllm9N9hf6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-88629-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88629
Nick Clifton <nickc at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at gcc dot gnu.org
--- Comment #13 from Nick Clifton <nickc at gcc dot gnu.org> ---
(In reply to prajwapa from comment #12)
> Could you please let me know, in which binutils version is this fixed?
Not really. I can confirm that the test cases do not fail when tested with
binutils 2.35 (with sanitization enabled) and with any binutils all the way
back to 2.30 if sanitization is not enabled.
Given that the bug was reported in 2018-12 and assuming that it was fixed at
some point in the 6 months after that, then the nearest binutils release that
would have included the fix is 2.33.
I hope that this helps.
Cheers
Nick
prev parent reply other threads:[~2021-01-12 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-88629-4@http.gcc.gnu.org/bugzilla/>
2020-05-07 12:15 ` trupti_pardeshi at persistent dot co.in
2020-05-07 12:49 ` wcventure at 126 dot com
2020-06-12 5:14 ` trupti_pardeshi at persistent dot co.in
2020-06-14 11:41 ` wcventure at 126 dot com
2020-06-15 7:54 ` trupti_pardeshi at persistent dot co.in
2021-01-12 7:44 ` prajwapa at in dot ibm.com
2021-01-12 11:23 ` nickc at gcc dot gnu.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-88629-4-qllm9N9hf6@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).