Hmm, I don't know if you have found the answer yet, and if you do, I'd like to know. My guess about the origin of your problem, if it is to do with you building boost yourself, is -fomit-frame-pointer. It is generally not a good idea compiling *libraries* with -fomit-frame-pointer, if you read the gcc doc and understand what it does. The frame-pointer is very important for subroutine entries and exits, and omiting it would often cause segmentation fault on initializing most library code. Thierry Dumont wrote:

I develop a C++ code which uses boost::threads

* This code performs perfectly well with the boost library wich comes with Debian sarge (libboost-thread1.32.0 for thread library).

But I want a more complete implementation of boost (I want to use property tree library). So I have installed and compiled boost_1_33_1.

* Using this library, all the programs which use the thread library segfault (at thread-create).

Where is the problem ?

With the Debian sarge library, I compile with the options:

-DBOOST_HAS_THREADS -D_REENTRANT -O2 -funroll-all-loops -fomit-frame-pointer

Do I need to change something? Did I missed something when I installed boost_1_33_1?

In both cases, g++ version is 3.3.5.

------------------------------------------------------------------------

_______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users