public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit 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: Mon, 31 Jan 2022 14:33:58 +0000 [thread overview] Message-ID: <bug-99935-4-Jh9JT60ZAJ@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 #10 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Nick Clifton <nickc@gcc.gnu.org>: https://gcc.gnu.org/g:f10bec5ffa487ad3033ed5f38cfd0fc7d696deab commit r12-6945-gf10bec5ffa487ad3033ed5f38cfd0fc7d696deab Author: Nick Clifton <nickc@redhat.com> Date: Mon Jan 31 14:28:42 2022 +0000 libiberty: Fix infinite recursion in rust demangler. libiberty/ PR demangler/98886 PR demangler/99935 * rust-demangle.c (struct rust_demangler): Add a recursion counter. (demangle_path): Increment/decrement the recursion counter upon entry and exit. Fail if the counter exceeds a fixed limit. (demangle_type): Likewise. (rust_demangle_callback): Initialise the recursion counter, disabling if requested by the option flags.
next prev parent reply other threads:[~2022-01-31 14:33 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 ` [Bug demangler/99935] " nickc at gcc dot gnu.org 2021-08-05 10:21 ` 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 [this message] 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-Jh9JT60ZAJ@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).