public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "nickc at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug demangler/99935] Stack exhaustion demangling rust mangled name Date: Fri, 07 May 2021 16:00:43 +0000 [thread overview] Message-ID: <bug-99935-4-wWER2oaIda@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-99935-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99935 --- Comment #1 from Nick Clifton <nickc at gcc dot gnu.org> --- Created attachment 50777 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50777&action=edit Proposed patch Here is a possible patch for the problem, adding a recursion limit to the demangle_path() function. Note - a variation of this bug appears to have been reported on the Ubuntu mailing lists with a different reproducer: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1925348
next prev parent reply other threads:[~2021-05-07 16:00 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-04-06 13:06 [Bug demangler/99935] New: " nickc at gcc dot gnu.org 2021-05-07 16:00 ` nickc at gcc dot gnu.org [this message] 2021-08-05 10:21 ` [Bug demangler/99935] " redi at gcc dot gnu.org 2021-08-11 15:07 ` nickc at gcc dot gnu.org 2022-01-22 17:54 ` pinskia at gcc dot gnu.org 2022-01-22 17:54 ` pinskia at gcc dot gnu.org 2022-01-22 17:54 ` pinskia at gcc dot gnu.org 2022-01-22 17:55 ` pinskia at gcc dot gnu.org 2022-01-22 17:55 ` pinskia at gcc dot gnu.org 2022-01-22 17:55 ` pinskia at gcc dot gnu.org 2022-01-26 15:31 ` nickc at gcc dot gnu.org 2022-01-31 14:33 ` cvs-commit at gcc dot gnu.org 2022-02-01 10:57 ` nickc 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-99935-4-wWER2oaIda@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).