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] New: Stack exhaustion demangling rust mangled name
Date: Tue, 06 Apr 2021 13:06:28 +0000 [thread overview]
Message-ID: <bug-99935-4@http.gcc.gnu.org/bugzilla/> (raw)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99935
Bug ID: 99935
Summary: Stack exhaustion demangling rust mangled name
Product: gcc
Version: 11.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: demangler
Assignee: unassigned at gcc dot gnu.org
Reporter: nickc at gcc dot gnu.org
Target Milestone: ---
The rust demangler can be pushed into an infinite loop, triggering stack
exhaustion:
% cat pr27963
# Reproduced from binutils PR 27963.
# Note - the expected output is wrong. It is just there as a placeholder.
--format=rust
_RIMBALO_suB_I__Z5printi
fred
% valgrind ./testsuite/test-demangle < pr27963
[...]
==429737== Stack overflow in thread #1: can't grow stack to 0x1ffe001000
[...]
=429737== Stack overflow in thread #1: can't grow stack to 0x1ffe001000
==429737== at 0x410BA7: demangle_path (rust-demangle.c:742)
[...]
Segmentation fault (core dumped)
next reply other threads:[~2021-04-06 13:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 13:06 nickc at gcc dot gnu.org [this message]
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
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@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: link
Be 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).