public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: snyder@fnal.gov To: gcc-gnats@gcc.gnu.org Subject: c++/9416: new parser: ICE in make_typename_type on invalid input Date: Thu, 23 Jan 2003 07:06:00 -0000 [thread overview] Message-ID: <200301230700.BAA06836@d0sgibnl1.fnal.gov> (raw) >Number: 9416 >Category: c++ >Synopsis: new parser: ICE in make_typename_type on invalid input >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: ice-on-illegal-code >Submitter-Id: net >Arrival-Date: Thu Jan 23 07:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: scott snyder >Release: 3.4 20030121 (experimental) >Organization: <organization of PR author (multiple lines)> >Environment: System: Linux karma 2.4.19-emp_2419p5a829i #1 Tue Sep 3 17:42:17 EST 2002 i686 unknown Architecture: i686 <machine, os, target, libraries (multiple lines)> host: i686-pc-linux-gnu build: i686-pc-linux-gnu target: i686-pc-linux-gnu configured with: ../gcc/configure --prefix=/usr/local/gcc --enable-threads=posix --enable-long-long >Description: g++ segfaults on the following (invalid) code. [sss@karma gcc]$ ./cc1plus y.cc void d0_DBObject::activate() y.cc:3: error: using `typename' outside of template y.cc:3: error: using `typename' outside of template y.cc:3: error: expected nested-name-specifier y.cc:3: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. $ Here's where it's crashing. Program received signal SIGSEGV, Segmentation fault. 0x080726aa in make_typename_type (context=0x0, name=0x4005c640, complain=tf_error) at ../../gcc/gcc/cp/decl.c:5509 5509 if (TREE_CODE (context) == NAMESPACE_DECL) (gdb) where #0 0x080726aa in make_typename_type (context=0x0, name=0x4005c640, complain=tf_error) at ../../gcc/gcc/cp/decl.c:5509 #1 0x08106a84 in cp_parser_postfix_expression (parser=0x40043898, address_p=false) at ../../gcc/gcc/cp/parser.c:3944 #2 0x08107d8a in cp_parser_unary_expression (parser=0x40043898, address_p=false) at ../../gcc/gcc/cp/parser.c:4688 #3 0x0810844d in cp_parser_cast_expression (parser=0x40043898, address_p=false) at ../../gcc/gcc/cp/parser.c:5111 #4 0x0810846e in cp_parser_pm_expression (parser=0x40043898) at ../../gcc/gcc/cp/parser.c:5131 #5 0x08112ecf in cp_parser_binary_expression (parser=0x40043898, token_tree_map=0x843e560, fn=0x8108455 <cp_parser_pm_expression>) at ../../gcc/gcc/cp/parser.c:13840 #6 0x08108523 in cp_parser_multiplicative_expression (parser=0x40043898) at ../../gcc/gcc/cp/parser.c:5186 #7 0x08112ecf in cp_parser_binary_expression (parser=0x40043898, token_tree_map=0x843e580, fn=0x8108502 <cp_parser_multiplicative_expression>) at ../../gcc/gcc/cp/parser.c:13840 #8 0x08108546 in cp_parser_additive_expression (parser=0x40043898) at ../../gcc/gcc/cp/parser.c:5210 #9 0x08112ecf in cp_parser_binary_expression (parser=0x40043898, token_tree_map=0x843e598, fn=0x8108525 <cp_parser_additive_expression>) >How-To-Repeat: ------------------ struct d0_DBObject { void activate() { (typename d0_Object)::activate();} }; ------------------ >Fix: <how to correct or work around the problem, if known (multiple lines)> >Release-Note: >Audit-Trail: >Unformatted:
next reply other threads:[~2003-01-23 7:06 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-01-23 7:06 snyder [this message] 2003-01-23 8:11 ehrhardt
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=200301230700.BAA06836@d0sgibnl1.fnal.gov \ --to=snyder@fnal.gov \ --cc=gcc-gnats@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).