public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "tbm at cyrius dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/29435] [4.1 Regression] segmentation fault Date: Wed, 11 Oct 2006 23:19:00 -0000 [thread overview] Message-ID: <20061011231928.20959.qmail@sourceware.org> (raw) In-Reply-To: <bug-29435-12387@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1194 bytes --] ------- Comment #4 from tbm at cyrius dot com 2006-10-11 23:19 ------- (gdb) where #0 0x000000000045a5ce in cxx_sizeof_or_alignof_type (type=0x2b29cf3e6b00, op=214, complain=1 '\001') at /home/tbm/scratch/gcc-4.1/gcc/cp/typeck.c:1251 #1 0x000000000044a947 in cp_parser_unary_expression (parser=0x2b29cf261460, address_p=0 '\0', cast_p=0 '\0') at /home/tbm/scratch/gcc-4.1/gcc/cp/parser.c:4850 #2 0x000000000044ae15 in cp_parser_assignment_expression (parser=0x2b29cf261460, cast_p=Variable "cast_p" is not available. ) at /home/tbm/scratch/gcc-4.1/gcc/cp/parser.c:5579 #3 0x000000000044ba72 in cp_parser_parenthesized_expression_list (parser=0x2b29cf261460, is_attribute_list=240 'â', cast_p=0 '\0', non_constant_p=0x0) at /home/tbm/scratch/gcc-4.1/gcc/cp/parser.c:4659 #4 0x000000000044a324 in cp_parser_unary_expression (parser=0x2b29cf261460, address_p=0 '\0', cast_p=1 '\001') at /home/tbm/scratch/gcc-4.1/gcc/cp/parser.c:4204 #5 0x000000000044ac41 in cp_parser_cast_expression (parser=0x2b29cf261460, address_p=0 '\0', cast_p=0 '\0') at /home/tbm/scratch/gcc-4.1/gcc/cp/parser.c:5455 ... -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29435
next prev parent reply other threads:[~2006-10-11 23:19 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-10-11 23:00 [Bug c++/29435] New: " tbm at cyrius dot com 2006-10-11 23:01 ` [Bug c++/29435] " tbm at cyrius dot com 2006-10-11 23:03 ` tbm at cyrius dot com 2006-10-11 23:06 ` pinskia at gcc dot gnu dot org 2006-10-11 23:19 ` tbm at cyrius dot com [this message] 2006-10-12 3:36 ` pinskia at gcc dot gnu dot org 2006-10-12 3:37 ` pinskia at gcc dot gnu dot org 2006-10-12 3:39 ` pinskia at gcc dot gnu dot org 2006-10-12 3:44 ` pinskia at gcc dot gnu dot org 2006-10-12 3:48 ` [Bug c++/29435] [4.1/4.2 " pinskia at gcc dot gnu dot org 2006-10-12 3:58 ` pinskia at gcc dot gnu dot org 2006-10-15 21:24 ` mmitchel at gcc dot gnu dot org 2006-10-16 17:38 ` [Bug c++/29435] [4.1/4.2 Regression] seg fault with sizeof and templates mmitchel at gcc dot gnu dot org 2006-10-16 23:06 ` mmitchel at gcc dot gnu dot org 2006-10-16 23:11 ` [Bug c++/29435] [4.1 " mmitchel at gcc dot gnu dot org 2006-10-17 1:56 ` mmitchel at gcc dot gnu dot org 2006-10-17 1:57 ` mmitchel at gcc dot gnu dot org 2006-11-03 18:30 ` pinskia at gcc dot gnu dot org 2006-12-02 7:35 ` pinskia at gcc dot gnu dot 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=20061011231928.20959.qmail@sourceware.org \ --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).