This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/53490] Segmentation Fault when accessing std::set
- From: "ja11sop at yahoo dot co.uk" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Sat, 26 May 2012 10:59:46 +0000
- Subject: [Bug c++/53490] Segmentation Fault when accessing std::set
- Auto-submitted: auto-generated
- References: <bug-53490-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53490
--- Comment #7 from Jamie Allsop <ja11sop at yahoo dot co.uk> 2012-05-26 10:59:46 UTC ---
(In reply to comment #6)
> (In reply to comment #4)
> > It was a vanilla bjam build of boost 1.49, so
> > no -std=c++11.
>
> Then technically that's not supported, since there are no guarantees of
> link-compatibility between -std=c++98 and -std=c++11 code (but I'm not aware of
> any specific reasons it wouldn't work for a std::set)
>
So after sifting through the jam files to confirm there is no -std=c++11 set in
boost for gcc4.7 I modified my bjam invocations to add cxxflags="-std=c++11"
and now the test runs without the segfault. Verifying now on the full code
base. When the tests cycle and presumably pass I'll post back. It does look
however as if the mismatch in compile flags is the culprit here. Apologies for
not being thorough in checking that earlier.