0005539: gcc on win64 buildslave segfaults

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0005539

Spring engine

Buildbot

public

2017-04-26 16:23

2017-05-09 03:54

Reporter

abma

Assigned To

TurBoss

Priority

normal

Severity

minor

Reproducibility

have not tried

Status

resolved

Resolution

fixed

Product Version

Target Version

Fixed in Version

Summary

0005539: gcc on win64 buildslave segfaults

Description

http://buildbot.springrts.com/builders/full-windows-x64/builds/1166/steps/buildConfigNinja/logs/stdio

In file included from /home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/bits/stl_map.h:63:0,
                 from /home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/map:61,
                 from ../../rts/System/FileSystem/ArchiveLoader.h:6,
                 from ../../rts/System/FileSystem/ArchiveLoader.cpp:4:
/home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/tuple: In instantiation of 'struct std::_Tuple_impl<0ull, std::__future_base::_Result_base*, std::__future_base::_Result_base::_Deleter>':
/home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/tuple:523:11: required from 'class std::tuple<std::__future_base::_Result_base*, std::__future_base::_Result_base::_Deleter>'
/home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/bits/unique_ptr.h:147:57: required from 'class std::unique_ptr<std::__future_base::_Result_base, std::__future_base::_Result_base::_Deleter>'
/home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/future:305:19: required from here
/home/jtoledano/mxe/usr/lib/gcc/x86_64-w64-mingw32.static/4.9.3/include/c++/tuple:231:12: internal compiler error: Segmentation fault
     struct _Tuple_impl<_Idx, _Head, _Tail...>
            ^
0xa0a4bf crash_signal
    /home/jtoledano/mxe/tmp-gcc-x86_64-w64-mingw32.static/gcc-4.9.3/gcc/toplev.c:337
x86_64-w64-mingw32.static-g++: internal compiler error: Segmentation fault (program cc1plus)
0x40c38a execute
    /home/jtoledano/mxe/tmp-gcc-x86_64-w64-mingw32.static/gcc-4.9.3/gcc/gcc.c:2854
Please submit a full bug report,
with preprocessed source if appropriate.
Please include the complete backtrace with any bug report.

Additional Information

very likely https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69802

-> fixed by using gcc 4.9.4, currently 4.9.3 is used on the buildslave

Tags

No tags attached.

Checked infolog.txt for Errors

Attached Files

Relationships

Relationships

Notes
~0017533 TurBoss (developer) 2017-04-27 12:27	Sorry I'm having hardware issues that cost money... will fix asap Sorry and thanks

~0017534 abma (administrator) 2017-04-27 12:30	oh, so not a software bug?

~0017535 abma (administrator) 2017-04-27 12:33	+ no worries, i created this issue as others asked for win64 builds as well, so i can point at it when asked again :-)

~0017536 TurBoss (developer) 2017-04-27 12:34	mxe compilation of gcc was giving segfault too fixed with apt install --reinstall cpp1-5 but once the compilation of gcc starts host freezes will keep you informed

~0017537 Kloot (developer) 2017-04-27 12:46	IME internal compiler errors like these forbode HDD failure.

~0017538 TurBoss (developer) 2017-04-27 12:49	was working well until a PSU failure that put the machine on a reboot loop Changed the psu and everything seemed well until this :D so HDD could be a candidate

~0017574 TurBoss (developer) 2017-05-08 21:18	ok I think I found the issue after change the HDDs I found the same problem but I noticed that the ram was hot because the cpu fan was changed and now air flows in horizontal not pointing to the motherboard so ram gets hot, I just put a small fan in the ram modules and now system seems stable atm is compiling... will see if finishes Thanks

~0017576 TurBoss (developer) 2017-05-09 03:50	finally http://buildbot.springrts.com/builders/full-windows-x64/builds/1182 filesystem was corrupt so I restored a backup

~0017577 TurBoss (developer) 2017-05-09 03:53	after 3 weeks I'm able to close my first issue :D sorry for the delay

Notes

Date Modified	Username	Field	Change
Issue History
2017-04-26 16:23	abma	New Issue
2017-04-26 16:25	abma	Assigned To	=> TurBoss
2017-04-26 16:25	abma	Status	new => assigned
2017-04-27 12:27	TurBoss	Note Added: 0017533
2017-04-27 12:30	abma	Note Added: 0017534
2017-04-27 12:33	abma	Note Added: 0017535
2017-04-27 12:34	TurBoss	Note Added: 0017536
2017-04-27 12:46	Kloot	Note Added: 0017537
2017-04-27 12:49	TurBoss	Note Added: 0017538
2017-05-08 21:18	TurBoss	Note Added: 0017574
2017-05-09 03:50	TurBoss	Note Added: 0017576
2017-05-09 03:53	TurBoss	Status	assigned => closed
2017-05-09 03:53	TurBoss	Resolution	open => fixed
2017-05-09 03:53	TurBoss	Note Added: 0017577
2017-05-09 03:54	TurBoss	Status	closed => resolved

Issue History