public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "samuel.hangouet at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/103563] New: ostream operator<< resolved to variant containing type resulting in stack overflow Date: Sun, 05 Dec 2021 10:41:44 +0000 [thread overview] Message-ID: <bug-103563-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103563 Bug ID: 103563 Summary: ostream operator<< resolved to variant containing type resulting in stack overflow Product: gcc Version: 11.1.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: samuel.hangouet at gmail dot com Target Milestone: --- Created attachment 51928 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=51928&action=edit Minimal test case. $ g++-11 --version g++-11 (Ubuntu 11.1.0-1ubuntu1~20.04) 11.1.0 (...) $ g++-11 -std=c++2a test.cpp -o test $ ./test Segmentation fault (core dumped) In my opinion, this file should not compile as no operator<< is provided for custom type V. Instead, the operator<< taking the variant which contains V is called, resulting in stack overflow at runtime.
next reply other threads:[~2021-12-05 10:41 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-05 10:41 samuel.hangouet at gmail dot com [this message] 2021-12-05 11:07 ` [Bug c++/103563] " pinskia at gcc dot gnu.org 2021-12-05 11:17 ` pinskia at gcc dot gnu.org 2021-12-06 16:09 ` m.cencora at gmail dot com 2021-12-15 10:10 ` samuel.hangouet 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-103563-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).