public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Igor A. Goussarov" <igusarov@mail.ru>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: debug/5335: ICE when DWARF-1 debug info is generated
Date: Fri, 21 Mar 2003 04:16:00 -0000	[thread overview]
Message-ID: <20030321041601.28808.qmail@sources.redhat.com> (raw)

The following reply was made to PR debug/5335; it has been noted by GNATS.

From: "Igor A. Goussarov" <igusarov@mail.ru>
To: bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	igusarov@akella.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: debug/5335: ICE when DWARF-1 debug info is generated
Date: Fri, 21 Mar 2003 07:14:35 +0300

 Hello Wolfgang,
 
     I've found that test case. In fact, it is not a specially written 
 test case, it is just a piece of preprocessed C++ code, very heavy on 
 templates. It has been manually reduced, eliminating a lot of unrelated 
 #includes, types, classes and member functions. What remains is about 
 25Kb file which contains several class templates and _one_ function that 
 takes one parameter of type "pointer to some complicated template class" 
 and has an empty function body. If I would have commented out this 
 function, the file would compile perfectly producing an empty .o file. 
 (I mean an object file with no one function in it, not a zero-sized 
 file). However, it doesn't look like the problem is in this particular 
 function. This function acts merely like a trigger, causing all of the 
 above templates to be instantiated at once. And it looks asif something 
 goes wrong during template instantiation (or generating dwarf debug info 
 for all these instantiated templates). Well... it's just my speculations...
     How do I send this file to you, then? You've told me not to send 
 attachments, and 1000 lines of code is too much to send in a mail body. 
 I can put its gzipped version somewhere to http, so you can download it. 
 Or upload it to your ftp.
 
 Cheers,
 Igor
 
 
 bangerth@dealii.org wrote:
 > Synopsis: ICE when DWARF-1 debug info is generated
 > 
 > State-Changed-From-To: open->feedback
 > State-Changed-By: bangerth
 > State-Changed-When: Fri Mar 14 02:47:14 2003
 > State-Changed-Why:
 >     Some kind of bitrot seems to have happened to this report
 >     while nobody was staring so hard at it all the time -- the
 >     attachment got corrupted. Do you still have the testcase
 >     you attached back then? I'd like to try to reproduce it,
 >     but without attachment...
 >     
 >     Thanks 
 >       Wolfgang
 > 
 > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=5335
 


             reply	other threads:[~2003-03-21  4:16 UTC|newest]

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

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=20030321041601.28808.qmail@sources.redhat.com \
    --to=igusarov@mail.ru \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).