public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "trupti_pardeshi at persistent dot co.in" <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: Mon, 15 Jun 2020 07:54:17 +0000	[thread overview]
Message-ID: <bug-88629-4-xqprkfYOoG@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

--- Comment #11 from Trupti Pardeshi <trupti_pardeshi at persistent dot co.in> ---
(In reply to Cheng Wen from comment #10)
> (In reply to Trupti Pardeshi from comment #9)
> 
> This bug can be reproduced in the commit version
> ebb8004a18a3808d7197762faf3c5aaeae82371f.
> 
> But now is fixed.

Thanks for reply Cheng. But could you please help me to know, the version of
binutils and version of gcc having the fix of this issue?

Knowing fixed-in version (of binutils and gcc) will be very helpful.

Looking forward for reply.

Many Thanks,
Trupti

  parent reply	other threads:[~2020-06-15  7:54 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 [this message]
2021-01-12  7:44 ` prajwapa at in dot ibm.com
2021-01-12 11:23 ` nickc at gcc dot gnu.org

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-xqprkfYOoG@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).