This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Simpler Bug Reporting
- To: <egcs at cygnus dot com>
- Subject: Simpler Bug Reporting
- From: junghelh at pe-nelson dot com
- Date: Wed, 07 Oct 98 17:21:59 -0800
How about adding some text to the ICE message? Something like:
"See http://egcs.cygnus.com/faq.html#bugreport for details," or a
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).
Maybe that would help cut down on this kind of traffic:
"Something isn't working."
"What's not working? See http://egcs.cygnus.com/faq.html#bugreport."
"Oh, you need more than a cut-n-paste of the error message..."
People are trying to help when they report these things; it should be
as simple as possible. Besides, the easier it is, the more likely
someone will actually report a problem. This is doubly true for less
experienced users. It goes without saying that reported bugs have a
much greater chance of being fixed than unreported bugs.
(Yes development resources are limited, but how much time is currently
spent asking people to read the FAQ and then resend their bug report?)