bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/29312] Stack overflow in demangle_const() and demangle_pat


From: nickc at redhat dot com
Subject: [Bug binutils/29312] Stack overflow in demangle_const() and demangle_path_maybe_open_generics(), cxxfilt
Date: Fri, 01 Jul 2022 11:12:02 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=29312

Nick Clifton <nickc at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nickc at redhat dot com
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |MOVED

--- Comment #2 from Nick Clifton <nickc at redhat dot com> ---
Hi Marsman1996,

  Good news / bad news:

  Bad news: This is the wrong place to report this bug.  
     The demangler is part of the libiberty library which is maintained
     by the gcc project.  The binutils just makes use of this library.

  Good news: The bug has already been reported:
     https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105039

  Bad news:  The patch that fixes the problem has not been reviewed or
     applied to the gcc sources.

  Good news: We are planning on making a new release of the binutils
     next month (2.39) and intend on making sure that the patch is in
     the binutils sources, even if it is not in the gcc sources.

  Bad news:  The patch only fixes one of your reproducers (demangle_const)
     The other reproducer still causes problems.

  Good news: I am investigating the second reproducer.

Conclusion:

  Please could you refile this bug report on the gcc bugzilla system.
  Maybe that will prompt someone to look at the situation again.  Plus
  it will give me somewhere to hang a second patch (assuming that I
  can create one) to fix the second reproducer.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]