[Bug binutils/22712] Stack Overflow (71959517)

2018-03-31 Thread jeremip11 at gmail dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22712

Jeremi  changed:

   What|Removed |Added

 CC||jeremip11 at gmail dot com

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils


[Bug binutils/22712] Stack Overflow (71959517)

2018-02-06 Thread nickc at redhat dot com
https://sourceware.org/bugzilla/show_bug.cgi?id=22712

Nick Clifton  changed:

   What|Removed |Added

 Status|UNCONFIRMED |RESOLVED
 CC||nickc at redhat dot com
 Resolution|--- |INVALID

--- Comment #1 from Nick Clifton  ---
Hi Google-Autofuzz,

  Thanks very much for reporting this problem.  Unfortunately bugs in the
  libiberty library, including the C++ name demangler, should be reported
  to the GCC project and not the binutils. 
(https://gcc.gnu.org/bugzilla/enter_bug.cgi?product=gcc component = demangler).

  The libiberty library is used by the binutils project, but it is not
  owned by it.  We try to keep the sources in the binutils repository
  in sync with the sources in the gcc repository, but there is no formal
  process for doing this.  So sometimes it may happen that a bug has been
  fixed in the gcc sources, but the patch has not yet been imported into
  the binutils sources.  If you find that this is the case, please do let
  us know so that we can fix the problem.

Cheers
  Nick

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
bug-binutils mailing list
bug-binutils@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-binutils