public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug demangler/110130] New: the rust demangling trap in long hangs , causing binutils/nm hangs for a long time to be killed.
@ 2023-06-05 16:14 swj22 at mails dot tsinghua.edu.cn
  2023-06-05 23:17 ` [Bug demangler/110130] " pinskia at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: swj22 at mails dot tsinghua.edu.cn @ 2023-06-05 16:14 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110130

            Bug ID: 110130
           Summary: the rust demangling trap in long hangs , causing
                    binutils/nm hangs for a long time to be killed.
           Product: gcc
           Version: rust/master
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: demangler
          Assignee: unassigned at gcc dot gnu.org
          Reporter: swj22 at mails dot tsinghua.edu.cn
  Target Milestone: ---

Created attachment 55264
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55264&action=edit
the test case

## Write in front ,  i use afl to fuzz binutils2.40-nm-new , and then find this
bug. Then i file the bug file to binutils/bugzilla . The answer is:
"""
This is a problem demangling the rust symbol _RYODGYODGpe__RYODGpe.
"""
So , i report bug to here .


## command i used: nm-new -C file

this test case , may make nm-new hang for much time until the system kill it ,
i have test it in ubuntu20.04 (compiler test: gcc 7.4 and 9.5). 

it seems like a infinite loop  , i use gdb to debug it , it behaves like
infinite loop , but my level is to low , can not analyse the root cause , so i
report the bug here.

## the attachment is the test case

^ permalink raw reply	[flat|nested] 2+ messages in thread

* [Bug demangler/110130] the rust demangling trap in long hangs , causing binutils/nm hangs for a long time to be killed.
  2023-06-05 16:14 [Bug demangler/110130] New: the rust demangling trap in long hangs , causing binutils/nm hangs for a long time to be killed swj22 at mails dot tsinghua.edu.cn
@ 2023-06-05 23:17 ` pinskia at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-06-05 23:17 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110130

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Depends on|                            |106622

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Most likely a dup of bug 106622.


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106622
[Bug 106622] Bug report: the endless looping in the rust demangler

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-06-05 23:17 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-05 16:14 [Bug demangler/110130] New: the rust demangling trap in long hangs , causing binutils/nm hangs for a long time to be killed swj22 at mails dot tsinghua.edu.cn
2023-06-05 23:17 ` [Bug demangler/110130] " 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).