public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug other/100968] New: libiberty: stuck in infinite loop in nm-new while demangling rust symbols
@ 2021-06-08 14:08 terrynini38514 at gmail dot com
2021-07-15 13:32 ` [Bug demangler/100968] " nickc at gcc dot gnu.org
2022-01-22 17:55 ` pinskia at gcc dot gnu.org
0 siblings, 2 replies; 3+ messages in thread
From: terrynini38514 at gmail dot com @ 2021-06-08 14:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100968
Bug ID: 100968
Summary: libiberty: stuck in infinite loop in nm-new while
demangling rust symbols
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: terrynini38514 at gmail dot com
Target Milestone: ---
Created attachment 50964
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50964&action=edit
demangling POC
Sorry for didn't identify the actual version of libiberty, but this bug can be
reproduce by clone the latest version (2.36.50) of binutils-gdb.
The POC cause nm-new stuck in infinite loop at rust-demangle.c:1024 and
rust-demangle.c:747 while using the nm-new with option -C, and there are more
similar case I found, I can attach them if needed. All of these cases just
stuck in a infinite loop in rust-demangle.c.
And I want to apply for CVE, if that requires me to do anything more, like
attach a valid patch or something ? Let me know, please.
Thanks.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug demangler/100968] libiberty: stuck in infinite loop in nm-new while demangling rust symbols
2021-06-08 14:08 [Bug other/100968] New: libiberty: stuck in infinite loop in nm-new while demangling rust symbols terrynini38514 at gmail dot com
@ 2021-07-15 13:32 ` nickc at gcc dot gnu.org
2022-01-22 17:55 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: nickc at gcc dot gnu.org @ 2021-07-15 13:32 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100968
Nick Clifton <nickc at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |nickc at gcc dot gnu.org
--- Comment #1 from Nick Clifton <nickc at gcc dot gnu.org> ---
Created attachment 51156
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51156&action=edit
Proposed patch
I think that this PR is a duplicate of 99935. The patch for that PR (attached
here) also fixes this problem.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug demangler/100968] libiberty: stuck in infinite loop in nm-new while demangling rust symbols
2021-06-08 14:08 [Bug other/100968] New: libiberty: stuck in infinite loop in nm-new while demangling rust symbols terrynini38514 at gmail dot com
2021-07-15 13:32 ` [Bug demangler/100968] " nickc at gcc dot gnu.org
@ 2022-01-22 17:55 ` pinskia at gcc dot gnu.org
1 sibling, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-01-22 17:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100968
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |RESOLVED
Resolution|--- |DUPLICATE
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Dup of bug 99935.
*** This bug has been marked as a duplicate of bug 99935 ***
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2022-01-22 17:55 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-06-08 14:08 [Bug other/100968] New: libiberty: stuck in infinite loop in nm-new while demangling rust symbols terrynini38514 at gmail dot com
2021-07-15 13:32 ` [Bug demangler/100968] " nickc at gcc dot gnu.org
2022-01-22 17:55 ` pinskia at gcc dot gnu.org
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).