public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "bsdfan3 at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/19171] <sys/reent.h> causes segfault ICE in GCC 4
Date: Tue, 28 Dec 2004 01:59:00 -0000	[thread overview]
Message-ID: <20041228015931.10438.qmail@sourceware.org> (raw)
In-Reply-To: <20041227213015.19171.bsdfan3@users.sourceforge.net>


------- Additional Comments From bsdfan3 at users dot sourceforge dot net  2004-12-28 01:59 -------
I finally figured out how to get a backtrace from the stage2 compiler, so here
it is (this is from running the posted testcase thru cc1):

--backtrace starts--
Starting program: /home/Lucas/b-gcc/gcc/cc1.exe /home/Lucas/test.i

Program received signal SIGSEGV, Segmentation fault.
0x00583da6 in emit_insn (x=0x101d19a0) at ../../gcc/gcc/emit-rtl.c:4375
4375      rtx last = last_insn;
(gdb) bt
#0  0x00583da6 in emit_insn (x=0x101d19a0) at ../../gcc/gcc/emit-rtl.c:4375
#1  0x00646f9c in ix86_handle_cdecl_attribute (node=0x22e614,
    name=0x101d7a48, args=0x0, flags=0, no_add_attrs=0x22e61b "")
    at ../../gcc/gcc/config/i386/i386.c:1716
#2  0x0040965f in decl_attributes (node=0x22e6f0, attributes=0x101da870,
    flags=0) at ../../gcc/gcc/attribs.c:253
#3  0x00405d9e in yyparse () at c-parse.y:1723
#4  0x004087c2 in c_parse_file () at c-parse.y:2922
#5  0x0047bf62 in c_common_parse_file (set_yydebug=0)
    at ../../gcc/gcc/c-opts.c:1092
#6  0x0049ec9b in compile_file () at ../../gcc/gcc/toplev.c:992
#7  0x004a079e in do_compile () at ../../gcc/gcc/toplev.c:2085
#8  0x004a0801 in toplev_main (argc=2, argv=0x10100f08)
    at ../../gcc/gcc/toplev.c:2117
#9  0x004972e0 in main (argc=2, argv=0x10100f08) at ../../gcc/gcc/main.c:35
--backtrace ends--

-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19171


  parent reply	other threads:[~2004-12-28  1:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-27 21:30 [Bug c/19171] New: " bsdfan3 at users dot sourceforge dot net
2004-12-27 21:32 ` [Bug c/19171] " bsdfan3 at users dot sourceforge dot net
2004-12-27 22:08 ` pinskia at gcc dot gnu dot org
2004-12-28  1:19 ` [Bug middle-end/19171] " bsdfan3 at users dot sourceforge dot net
2004-12-28  1:20 ` pinskia at gcc dot gnu dot org
2004-12-28  1:23 ` bsdfan3 at users dot sourceforge dot net
2004-12-28  1:28 ` pinskia at gcc dot gnu dot org
2004-12-28  1:29 ` pinskia at gcc dot gnu dot org
2004-12-28  1:29 ` pinskia at gcc dot gnu dot org
2004-12-28  1:31 ` bsdfan3 at users dot sourceforge dot net
2004-12-28  1:59 ` bsdfan3 at users dot sourceforge dot net [this message]
2004-12-28  5:02 ` pinskia at gcc dot gnu dot org
2004-12-28 14:27 ` bsdfan3 at users dot sourceforge dot net
2004-12-30  1:25 ` bsdfan3 at users dot sourceforge dot net

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=20041228015931.10438.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: link
Be 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).