This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re[2]: Simpler Bug Reporting
- To: Hans-Peter Nilsson <hans-peter dot nilsson at axis dot com>, egcs at cygnus dot com, oliva at dcc dot unicamp dot br
- Subject: Re[2]: Simpler Bug Reporting
- From: Henric Jungheim <junghelh at pe-nelson dot com>
- Date: Wed, 14 Oct 1998 13:33:16 -0700
>Author: Hans-Peter Nilsson <hans-peter.nilsson@axis.com> at smtplink-pen
>Date: 10/11/98 2:16 AM
>> From: junghelh@pe-nelson.com
>> How about adding some text to the ICE message? Something like:
>> "See http://egcs.cygnus.com/faq.html#bugreport for details," or a
>
>I was going to ask this again myself anyday, but as it came up
>now, let's start a refresh cycle.
:)
>> summary of the stuff on the web page. One could get a little fancier
>> and create a dump file with the compiler version, host type, and
>> command line. Or perhaps the compiler could spit out a copy of the
>> exact command line the user should use to get the intermeditate files
>> (including the flags that were in effect).
>I like this idea. I'm sure you'll get quite a few cheers if you
>send in patches for improvements. I'd do it, but it was your
Cheers, huh? Well, I'm more than a little reluctant to go poking into
software systems I don't fully understand. The "Hmm, I wonder what this
does," approach has some definite reliability implications...
>idea, and my ego needs an ACK for the other patches ;-) or
>maybe I'm waiting for the copyright assignment ACK before doing
>further work.
Heheh... The thing to always remember is that people are far more likely
to make noise about something that *doesn't* work. Granted if your
patches
aren't integrated, then you loose even this gratification.
Anyway, I mentioned my idea on the off chance that the infamous
"somebody"
might be interested in contributing something that doesn't require
jumping
directly into the deep magic compiler stuff. (And has time, etc., etc.)