Re: how to report a bug which doesn't happen on the .ii file generated with -save-temps?

[Francesco Montorsi <f18m_cpp217828 at yahoo dot it>]

Hi,

Ian Lance Taylor ha scritto:
> 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.
ok, thanks for the info; I'll post there in future.

> > 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?
yes, I am!
In fact, removing the PCH and recreating it fixed the problem! Thanks for the hint.

> > 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.
hmmm, actually I didn't make a backup copy of the damaged PCH and so I cannot 
reproduce the bug anymore myself :/

I suspect that the problem comes from using "make -j4" (on a quadcore system): 
sometimes the PCH files get corrupted and problems like the one reported above 
happen. It maybe a race condition somewhere...

For now I think I won't spend time any further on this - since I have no 
reliable way to reproduce the bug in the PCH; if I hit it once again, I'll try 
to save the damaged PCH (in the hope it's useful to somebody to understand 
what's wrong)...

Thanks,
Francesco