public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kuba dot skowron at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/32008] New: g++ crashes (internal error) on simple code. Date: Sun, 20 May 2007 10:58:00 -0000 [thread overview] Message-ID: <bug-32008-14574@http.gcc.gnu.org/bugzilla/> (raw) g++ hangs computer for about 5 minutes, then reports "internal error". On program: #include <iostream> #include <string> using namespace std; int main() { cout << "\e[18t" << flush string s; return 0; } Compiled with: g++ -c gcc_bug.cpp He should report "expected ';'" error on line 9 (after flush, before string s), but instead computer becomes not responsive, and finally g++ is being killed by the OS. This bug is triggerd by invalid code, but forgeting about ';' at the end of the line is very common and cause in this particular situation very severe effect. When I don't use "using namespace std;", but explicitly write std::cout, std::flush and std::string, g++ works as he should. Occurs on: gcc version 3.3.5 20050117 (prerelease) (SUSE Linux) Also occurs on: g++ (GCC) 3.3.3 20040412 (Red Hat Linux 3.3.3-7) Doesn't occur on: g++ (GCC) 4.0.3 20060212 (prerelease) (Debian 4.0.2-9) Additional information: output from g++ triggered by g++ -v -save-temps gcc_bug.cpp can be found at: http://studenci.fuw.edu.pl/~jskow/www/gcc_bug.out preprocessed file can be found at: http://studenci.fuw.edu.pl/~jskow/www/gcc_bug.ii -- Summary: g++ crashes (internal error) on simple code. Product: gcc Version: 3.3.5 Status: UNCONFIRMED Severity: major Priority: P3 Component: c++ AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: kuba dot skowron at gmail dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32008
next reply other threads:[~2007-05-20 10:58 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-05-20 10:58 kuba dot skowron at gmail dot com [this message] 2007-05-20 11:05 ` [Bug c++/32008] " kuba dot skowron at gmail dot com 2007-05-20 11:07 ` kuba dot skowron at gmail dot com 2007-05-20 12:29 ` pcarlini at suse dot de
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-32008-14574@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).