public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: igusarov@akella.com
To: gcc-gnats@gcc.gnu.org
Subject: debug/5335: ICE when DWARF-1 debug info is generated
Date: Wed, 09 Jan 2002 06:26:00 -0000	[thread overview]
Message-ID: <20020109142520.31930.qmail@sources.redhat.com> (raw)


>Number:         5335
>Category:       debug
>Synopsis:       ICE when DWARF-1 debug info is generated
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          ice-on-legal-code
>Submitter-Id:   net
>Arrival-Date:   Wed Jan 09 06:26:01 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Igor A. Goussarov
>Release:        Reading specs from /usr/lib/gcc-lib/i386-unknown-freebsd4.4/3.0.3/specs   Configured with: ./configure --prefix=/usr   Thread model: posix   gcc version 3.0.3
>Organization:
>Environment:
i386-FreeBSD-4.4-RELEASE
>Description:
The attached file compiles fine if no debug info is 
requested or if DWARF-2 debug info is requested.
However, compilation with -gdwarf+, -gdwarf+1, gdwarf+2 
or -gdwarf+3 switch results in ICE:

../IGusarov/Lists.h:821: Internal compiler error in dwarfout_finish, at
   dwarfout.c:6532
Please submit a full bug report,
with preprocessed source if appropriate.
See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions.

It looks like generating this debug info requires some 
more templated types (which were a member 'typedefs' in 
another templated type) to be instantiated and these
freshly instantiated types are left in pending_types_list
which violates the final assertion in dwarfout_finish
and thus lead to abort()...
>How-To-Repeat:
unpack an archived "TemplateElements_.i" file and run
g++ -c -gdwarf+3 TemplateElements_.i
>Fix:
Don't use dwarf-1 debug format. In fact, I've
toyed with various debug info formats and found that
4 out of approx. 120 source files in my current project 
fails with the same ICE if compiled with one of 
-gdwarf+[123]
>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="TemplateElements_.i.gz"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="TemplateElements_.i.gz"


             reply	other threads:[~2002-01-09 14:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09  6:26 igusarov [this message]
2003-03-14  2:47 bangerth
2003-03-21  4:16 Igor A. Goussarov
2003-03-21 16:16 Wolfgang Bangerth
2003-03-22 19:02 bangerth
2003-03-22 19:05 bangerth
2003-03-22 22:36 Daniel Jacobowitz
2003-03-24 15:42 bangerth

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=20020109142520.31930.qmail@sources.redhat.com \
    --to=igusarov@akella.com \
    --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: 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).