public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "bajinsheng at outlook dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug other/99763] New: c++filt crashes when demangling Date: Thu, 25 Mar 2021 07:49:13 +0000 [thread overview] Message-ID: <bug-99763-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99763 Bug ID: 99763 Summary: c++filt crashes when demangling Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other Assignee: unassigned at gcc dot gnu.org Reporter: bajinsheng at outlook dot com Target Milestone: --- the payload to trigger the crash The bug is about segment fault, which may be caused by endless loop. Source code repository: git://sourceware.org/git/binutils-gdb.git commit: 12af5ebd820425e8ad843a1dac687a2fffc4a2e3 Date: Tue Mar 23 00:00:07 2021 +0000 Compiler: Clang-12 OS: Ubuntu 16.04.7 LTS The call stack of the bug: #0 0x00000000004beff1 in demangle_path (rdm=rdm@entry=0x7ffe5ead2850, in_value=in_value@entry=1) at ./rust-demangle.c:664 #1 0x00000000004bf4d8 in demangle_path (rdm=rdm@entry=0x7ffe5ead2850, in_value=in_value@entry=1) at ./rust-demangle.c:774 ……….. #52364 0x00000000004bf4d8 in demangle_path (rdm=rdm@entry=0x7ffe5ead2850, in_value=in_value@entry=1) at ./rust-demangle.c:774 #52365 0x00000000004bf4d8 in demangle_path (rdm=rdm@entry=0x7ffe5ead2850, in_value=in_value@entry=1) at ./rust-demangle.c:774 #52366 0x00000000004be5f0 in rust_demangle_callback (mangled=<optimized out>, options=267, callback=<optimized out>, opaque=0x7ffe5ead28d0) at ./rust-demangle.c:1400 #52367 0x00000000004bf8d2 in rust_demangle (mangled=0x7ffe5ead2850 "\302sq", options=1) at ./rust-demangle.c:1511 #52368 0x00000000004a4a0d in cplus_demangle (mangled=0x7173c0 <main.mbuffer> "_RB_R", options=267) at ./cplus-dem.c:166 I upload the payload to reproduce the bug: cat payload | ./c++filt
next reply other threads:[~2021-03-25 7:49 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-25 7:49 bajinsheng at outlook dot com [this message] 2021-03-25 7:52 ` [Bug other/99763] " bajinsheng at outlook dot com 2021-03-25 9:41 ` marxin at gcc dot gnu.org 2021-03-25 10:14 ` bajinsheng at outlook dot com 2021-03-25 10:14 ` bajinsheng at outlook dot com 2021-03-25 10:19 ` marxin at gcc dot gnu.org 2021-03-25 10:20 ` bajinsheng at outlook dot com 2021-03-25 10:22 ` marxin at gcc dot gnu.org 2021-03-25 10:22 ` marxin at gcc dot gnu.org 2021-03-25 10:28 ` bajinsheng at outlook dot com 2021-12-27 8:25 ` [Bug demangler/99763] " pinskia at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-99763-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).