Re: need help with gcc segfault on i686

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 08/12/2016 11:36 AM, Till Hofmann wrote:
Hi all,

gprolog has been FTBFS for a while due to a segfault on i686, see this
build [1] for an example. I followed advice on [2] to add some debugging
flags, not sure if they really help though without access to dumped files.
The segfault occurs while compiling this file [3].

We need the .i file that is left behind by -save-temps, and the compiler command line which triggers the crash. See the instructions here:

  <https://gcc.gnu.org/bugs/>

Please make sure that the .i file reproduces the bug with the command line (using the .i file instead of the .c file). The file a bug (either against the Fedora gcc package, or on gcc.gnu.org Bugzilla), include the GCC command line, specify the exact GCC version, and attach the .i file.

The GCC developers will take it from there.

[2] https://gcc.gnu.org/bugs/segfault.html

This resource is not targeted at end users reporting bugs. Sorry if that's not clear.

Thanks,
Florian
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://lists.fedoraproject.org/admin/lists/devel@xxxxxxxxxxxxxxxxxxxxxxx




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux