Re: Patches to the FAQ and the fatal error messages for guiding bug-reports better

[Robert Lipe <robertl at dgii dot com>]

This looks pretty promising to me.

Have we accepted that the entire EGCS community is web-enabled?   I don't
have any difficulty with that concept.

> Index: egcs/gcc/f/g77spec.c
> ===================================================================
> RCS file: /egcs/carton/cvsfiles/egcs/gcc/f/g77spec.c,v
> retrieving revision 1.12
> diff -p -c -r1.12 g77spec.c
> *** g77spec.c	1998/07/21 22:34:23	1.12
> --- g77spec.c	1998/08/25 01:12:44
> *************** code-generation methodology, and so on.\
> *** 427,433 ****
>   For more information on g77 and gcc, type the commands `info -f g77'\n\
>   and `info -f gcc' to read the Info documentation.\n\
>   \n\
> ! Report bugs to <egcs-bugs@cygnus.org>.\n");
>   	  exit (0);
>   	  break;
>   #endif
> --- 427,435 ----
>   For more information on g77 and gcc, type the commands `info -f g77'\n\
>   and `info -f gcc' to read the Info documentation.\n\
>   \n\
> ! Report bugs to <egcs-bugs@cygnus.org>, but first see the\n\
> ! documentation (section Bugs), the file BUGS (included with the source)\n\
> ! or <URL:http://egcs.cygnus.com/faq.html#bugreport>.\n");
>   	  exit (0);
>   	  break;
>   #endif

s/org/com/

> +   <li>Preprocessed output of the source file that caused the compiler error
> + </ul>

I have mixed feelings about this, having just earlier in the day
corrected a testcase bug that was a direct result of this.  OTOH, it's
probably easier for us to deprocess (that's the opposite of preprocess :-) 
the system headers back out of the file than it would be for us to
get users to synthesize reduced testcases....

> + <p>All this can normally be accomplished by mailing the command line, the
> + output of the command, and the resulting `<tt><i>your-file</i>.i</tt>' for C,
> + or `<tt><i>your-file</i>.ii</tt>' for C++, corresponding to:
> + 
> + <p><tt>egcs -v --save-temps <i>all-your-options</i> <i>your-file</i>.c</tt>

Could this be simplified to something like "... accomplished by adding   
--save-temps to the command line, running the command, then sending the 
generated .i  and the full command issued to..."


This idea looks pretty promising to me.   Thanx for the effort.

RJL