public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hededrk at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/96345] New: __cxa demangle fails to demangle a very long string Date: Mon, 27 Jul 2020 19:55:37 +0000 [thread overview] Message-ID: <bug-96345-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96345 Bug ID: 96345 Summary: __cxa demangle fails to demangle a very long string Product: gcc Version: 10.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libstdc++ Assignee: unassigned at gcc dot gnu.org Reporter: hededrk at gmail dot com Target Milestone: --- I found this bug because one of my tests started to fail (not sure when it started to fail because I've set up CI only yesterday). I assume this is a bug because GCC is able to produce such names. Steps to reproduce: 1. compile attached file g++ -c cxa_demangle_fail.cpp 2. obtain mangled name with nm nm cxa_demangle_fail.o 3. pass that name into abi::__cxa_demangle auto name = /*long string*/; size_t size = 1024; auto memory = static_cast<char*>(malloc(size)); int status; auto demangled = abi::__cxa_demangle(name, memory, &size, &status); Result: __cxa_demangle fails with code -2.
next reply other threads:[~2020-07-27 19:55 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-07-27 19:55 hededrk at gmail dot com [this message] 2020-07-27 19:57 ` [Bug libstdc++/96345] " hededrk at gmail dot com 2020-07-27 19:58 ` hededrk at gmail dot com 2020-07-27 21:18 ` pinskia at gcc dot gnu.org 2020-07-28 4:49 ` hededrk at gmail dot com 2020-07-28 8:50 ` hededrk at gmail dot com 2022-05-30 9:39 ` [Bug demangler/96345] " hededrk at gmail dot com
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-96345-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).