[Bug c++/53455] boost::python segfault

redi at gcc dot gnu.org gcc-bugzilla@gcc.gnu.org
Thu Jun 14 13:22:00 GMT 2012


--- Comment #14 from Jonathan Wakely <redi at gcc dot gnu.org> 2012-06-14 13:21:59 UTC ---
(In reply to comment #0)
> I tried boost as delivered with fedora 17, a home-compiled version with
> -std=c++11 and a home-compiled version without c++11. The c++11 flag on the
> _library_ does not seem to influence the problem, although the value change is
> inside the library. However, when turning off c++11 for the testing program
> (going to attach the .ii too), it works fine.

Are you sure you built boost with -std=c++11 correctly?

If I build libboost_python.so with -std=c++11 and then compile crashtest.cpp
with -std=c++11 it works fine, likewise building both with -std=c++98. It only
crashes when mixing c++98 library with c++11 code, or vice versa (which is
consistent with PR 53657)

More information about the Gcc-bugs mailing list