Re: [boost] filesystem segfault on startup

Subject: Re: [boost] filesystem segfault on startup
From: Andrey Semashev (andrey.semashev_at_[hidden])
Date: 2014-04-16 02:47:06

On Wed, Apr 16, 2014 at 12:46 AM, Biddiscombe, John A. <biddisco_at_[hidden]> wrote:
> I’m using a BGQ machine and have compiled boost 1_55 using gcc4.8.2, the application I am testing does not use filesystem itself, but the libraries it pulls in do. On startup I have segfaults with a stack trace like this (below)
>
> Can anyone tell what is going wrong (lots of locale related problems on this machine it seems). I have no knowledge of boost.filesystem internals and I would like to work around this if possible.
>
> Thanks
>
> JB
>
> #0  0x00000080a0b272f4 in ._dl_fixup () from /lib64/ld64.so.1
> #1  0x00000080a0b2fd78 in ._dl_runtime_resolve () from /lib64/ld64.so.1
> #2  0x00000fffb6ef9384 in ._ZN5boost10filesystem18directory_iteratorC1Ev ()
>     at /gpfs/bbp.cscs.ch/home/biddisco/apps/gcc-4.8.2/boost_1_55_0/include/boost/filesystem/operations.hpp:676
> #3  0x00000fffb3aace44 in ._Z41__static_initialization_and_destruction_0ii () at libs/filesystem/src/operations.cpp:248
> #4  0x00000fffb3aacf2c in ._GLOBAL__sub_I_operations.cpp () at libs/filesystem/src/operations.cpp:2230
> #5  0x00000fffb3ab8a78 in .__do_global_ctors_aux ()
>    from /gpfs/bbp.cscs.ch/home/biddisco/apps/gcc-4.8.2/boost_1_55_0/lib/libboost_filesystem.so.1.55.0
> #6  0x00000fffb3aa32e4 in ._init () from /gpfs/bbp.cscs.ch/home/biddisco/apps/gcc-4.8.2/boost_1_55_0/lib/libboost_filesystem.so.1.55.0
> #7  0x00000080a0b27bf0 in ._dl_init_internal () from /lib64/ld64.so.1
> #8  0x00000080a0b154dc in ._dl_start_user () from /lib64/ld64.so.1

I don't know what the problem is but quick googling resulted in this
topic, which looks similar:

http://stackoverflow.com/questions/10578315/segmentation-fault-in-dl-runtime-resolve

My first guess is this has something to do with symbol relocation at
load time. Check that you're not mixing different versions of Boost or
other libs. Try to remove some libs you link with until you can
pinpoint the problematic combination.