public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/11654] gcc seg fault when using pre-compiled headers and -gstabs Date: Thu, 24 Jul 2003 02:33:00 -0000 [thread overview] Message-ID: <20030724023303.3895.qmail@sources.redhat.com> (raw) In-Reply-To: <20030724021919.11654.gcc@tridgell.net> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=11654 pinskia at physics dot uc dot edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed| |1 GCC target triplet|i686-pc-linux-gnu |*-*-* Keywords| |ice-on-valid-code Last reconfirmed|0000-00-00 00:00:00 |2003-07-24 02:33:02 date| | ------- Additional Comments From pinskia at physics dot uc dot edu 2003-07-24 02:33 ------- I can confirm this on the mainline (20030723). emit_pending_bincls () at /home/gates/pinskia/src/gnu/gcc/src/gcc/dbxout.c:592 592 f = f->next; (gdb) bt #0 emit_pending_bincls () at /home/gates/pinskia/src/gnu/gcc/src/gcc/dbxout.c:592 #1 0x080fc435 in dbxout_symbol (decl=0x400918dc, local=0) at /home/gates/pinskia/src/gnu/ gcc/src/gcc/dbxout.c:580 #2 0x080fed21 in dbxout_begin_function (decl=0x400918dc) at /home/gates/pinskia/src/gnu/ gcc/src/gcc/dbxout.c:3188 #3 0x08317abb in assemble_start_function (decl=0x400918dc, fnname=0x85389dd "test") at /home/gates/pinskia/src/gnu/gcc/src/gcc/varasm.c:1087 #4 0x082f87bd in rest_of_handle_final (decl=0x400918dc, insns=0x4004c3e0) at /home/gates/ pinskia/src/gnu/gcc/src/gcc/toplev.c:1987 #5 0x082fae7f in rest_of_compilation (decl=0x400918dc) at /home/gates/pinskia/src/gnu/gcc/ src/gcc/toplev.c:3502 #6 0x0806d1a2 in c_expand_body_1 (fndecl=0x400918dc, nested_p=0) at /home/gates/pinskia/ src/gnu/gcc/src/gcc/c-decl.c:6425 #7 0x0806d709 in c_expand_body (fndecl=0x1) at /home/gates/pinskia/src/gnu/gcc/src/gcc/c- decl.c:6507 #8 0x0806ccea in finish_function (nested=0, can_defer_p=1) at /home/gates/pinskia/src/gnu/ gcc/src/gcc/c-decl.c:6295 #9 0x0804b4a9 in yyparse () at c-parse.y:385 #10 0x0805213b in c_parse_file () at c-parse.y:3022 #11 0x0809ad3b in c_common_parse_file (set_yydebug=1) at /home/gates/pinskia/src/gnu/gcc/ src/gcc/c-opts.c:1211 #12 0x082f80ca in compile_file () at /home/gates/pinskia/src/gnu/gcc/src/gcc/toplev.c:1749 #13 0x082fca8e in do_compile () at /home/gates/pinskia/src/gnu/gcc/src/gcc/toplev.c:4526 #14 0x082fcba5 in toplev_main (argc=1, argv=0xbffec514) at /home/gates/pinskia/src/gnu/gcc/ src/gcc/toplev.c:4567 #15 0x420174d9 in __libc_start_main () from /lib/i686/libc.so.6 #16 0x08049a11 in _start () (gdb) p f $1 = (struct dbx_file *) 0x0
next prev parent reply other threads:[~2003-07-24 2:33 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-24 2:19 [Bug c/11654] New: " gcc at tridgell dot net 2003-07-24 2:33 ` pinskia at physics dot uc dot edu [this message] 2003-07-24 2:48 ` [Bug pch/11654] " pinskia at physics dot uc dot edu 2003-07-24 6:46 ` geoffk at geoffk dot org 2003-07-24 11:12 ` pinskia at physics dot uc dot edu 2003-11-07 22:12 ` cvs-commit at gcc dot gnu dot org 2003-12-16 18:19 ` geoffk at gcc dot gnu dot org 2003-12-19 10:01 ` 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=20030724023303.3895.qmail@sources.redhat.com \ --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).