[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug binutils/27965] nm-new stuck in infinite loop while demangling rust
From: |
terrynini38514 at gmail dot com |
Subject: |
[Bug binutils/27965] nm-new stuck in infinite loop while demangling rust symbol |
Date: |
Tue, 08 Jun 2021 10:03:11 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=27965
--- Comment #2 from terrynini38514 at gmail dot com ---
Thank you very much, I'm waiting gcc to create my account for reporting.
amodra at gmail dot com <sourceware-bugzilla@sourceware.org> 於 2021年6月8日 週二
上午11:34寫道:
> https://sourceware.org/bugzilla/show_bug.cgi?id=27965
>
> Alan Modra <amodra at gmail dot com> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |RESOLVED
> Resolution|--- |MOVED
> Assignee|unassigned at sourceware dot org |amodra at gmail
> dot com
>
> --- Comment #1 from Alan Modra <amodra at gmail dot com> ---
> I've verified that your testcase does cause infinite recursion and a
> segfault,
> both with current binutils and with libiberty/rust-demangle.c from gcc,
> however
> gcc is the project that owns libiberty. The correct place to report
> problems
> in the demangler is https://gcc.gnu.org/bugzilla/. I've marked this bug
> as
> moved but will leave it up to you to create a new gcc bug.
>
> --
> You are receiving this mail because:
> You reported the bug.
--
You are receiving this mail because:
You are on the CC list for the bug.