LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   [bugreport ]GCC segmentation fault (https://www.linuxquestions.org/questions/slackware-14/%5Bbugreport-%5Dgcc-segmentation-fault-4175581373/)

Future Shock 06-03-2016 12:26 PM

[bugreport ]GCC segmentation fault
 
Slackware64-current, GCC 5.3
Code:

$ g++ bug.cc -std=c++1y -c -o bug.o
In file included from /usr/include/boost/functional/hash/hash.hpp:20:0,
                from /usr/include/boost/functional/hash.hpp:6,
                from /home/user/src/evernus/ExternalOrderImporter.h:20,
                from /home/user/src/evernus/EveCentralExternalOrderImporter.h:19,
                from /home/user/src/evernus/EveCentralExternalOrderImporter.cpp:17:
/usr/lib/gcc/x86_64-pc-linux-gnu/5.3.0/include/g++-v5/functional: In constructor «std::function<_Res(_ArgTypes ...)>::function(_Functor) [with _Functor = Evernus::EveCentralExternalOrderImporter::fetchExternalOrders(const TypeLocationPairs&) const::<lambda(auto:1&&, const auto:2&)>; <template-parameter-2-2> = void; _Res = void; _ArgTypes = {std::vector<Evernus::ExternalOrder, std::allocator<Evernus::ExternalOrder> >&&, const QString&}]»:
/usr/lib/gcc/x86_64-pc-linux-gnu/5.3.0/include/g++-v5/functional:2250:7: внутренняя ошибка компилятора: Ошибка сегментирования
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.

Quote:

внутренняя ошибка компилятора: Ошибка сегментирования
means smth like
Quote:

inner error of compiler: segmentation fault
the sources are here ==> https://bpaste.net/raw/48d0da50fd14

ponce 06-03-2016 12:43 PM

hi Future Shock,

sorry, but I think you missed reading the last line of the block you pasted, where it's specified how to do the bug report and where to post it.
Code:

See <http://gcc.gnu.org/bugs.html> for instructions.

Future Shock 06-03-2016 03:58 PM

Quote:

Originally Posted by ponce (Post 5555359)
hi Future Shock,

sorry, but I think you missed reading the last line of the block you pasted, where it's specified how to do the bug report and where to post it.
Code:

See <http://gcc.gnu.org/bugs.html> for instructions.

The issue might be fixed in newer versions of gcc. If so, The Man maybe should upgrade Slackware's gcc up to the fixed version in current.

bassmadrigal 06-03-2016 04:01 PM

GCC was last upgraded back in December (there were a few rebuilds for various changes since then, but still on the same version).

It is way too far in the dev cycle of 14.2 to be bumping GCC to a newer version.

EDIT: And Pat already commented earlier today on a newer GCC and implying it won't be added this cycle.

ponce 06-03-2016 04:04 PM

Quote:

Originally Posted by Future Shock (Post 5555505)
The issue might be fixed in newer versions of gcc. If so, The Man maybe should upgrade Slackware's gcc up to the fixed version in current.

but you are not sure that this issue has been fixed, right? the only way to find out is if you file a bug report to the gcc developers and they confirm you that.

also, please see here.

55020 06-03-2016 04:43 PM

The usual workround is -- if gcc has a bug, use clang.

e.g.
https://slackbuilds.org/cgit/slackbu...oot.SlackBuild
https://slackbuilds.org/cgit/slackbu...hdr.SlackBuild


All times are GMT -5. The time now is 02:25 PM.