This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: how to report a bug which doesn't happen on the .ii file generated with -save-temps?
- From: Ian Lance Taylor <iant at google dot com>
- To: Francesco Montorsi <f18m_cpp217828 at yahoo dot it>
- Cc: gcc at gcc dot gnu dot org
- Date: Fri, 13 Mar 2009 14:03:12 -0700
- Subject: Re: how to report a bug which doesn't happen on the .ii file generated with -save-temps?
- References: <gpee47$2j4$1@ger.gmane.org>
Francesco Montorsi <f18m_cpp217828@yahoo.it> writes:
> I'm new to GCC project so let me know if this is the wrong place
> where I can ask such a question.
The mailing list gcc-help@gcc.gnu.org would be a better place.
> I've found a bug in Gcc 4.3.3 (on machine "Linux ubuntu
> 2.6.28-9-generic #31-Ubuntu SMP Wed Mar 11 15:43:49 UTC 2009 x86_64
> GNU/Linux") which I can reliably reproduce (just running "make") and
> which generates:
>
> g++ -c ....lots of other options... ../src/stc/stc.cpp
> g++: Internal error: Segmentation fault (program cc1plus)
> Please submit a full bug report.
> See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions.
> make: *** [stclib_stc.o] Errore 1
>
> However if I try to follow README.Bugs and use the -save-temps option
> and then try to compile the generated .ii file:
>
> g++ -c ....lots of other options... stc.ii
>
> the crash doesn't happen.
It may not matter. As long as the crash happens when you use the
--save-temps option, then reporting the bug with the .ii file may be
enough. However, it's true that if other people are unable to recreate
the problem then it may not be possible to fix it.
Sometimes this can indicate that there is a problem with precompiled
haders. Do you know if you are using a precompiled header?
> How can I report such a bug? Including all involved files in a tarball
> would violate the rules for reporting bugs.
Do it anyhow if that is the only way.
Ian