iOS build OK But I null

[zgbilltalent]

When I Use the Version of 1.77.0 in my app ，It will crash ，

boost::filesystem::recursive_directory_iterator endIter;
for (boost::filesystem::recursive_directory_iterator iter(p); iter != endIter; iter++) {
if (boost::filesystem::is_directory(*iter)) {
std::cout << "key:EEEEEE " << std::endl;
std::cout << iter->path().string() << std::endl;
std::cout << "key:EEEEEE " << std::endl;
} else {
std::cout << "is a file" << std::endl;
std::cout << "key:EEEEEE " << std::endl;
std::cout << iter->path().string() << std::endl;
std::cout << "key:EEEEEE " << std::endl;
}
}

[Lastique]

Can you provide more details? What's the backtrace? What does the filesystem tree look like?

[zgbilltalent]

What should I do next? Re compile or something with my using way ?

[Lastique]

I have no idea. You still haven't provided any details. Try debugging the problem on your end.

[zgbilltalent]

How Can I give you the code ?zip?

[zgbilltalent]

please Check it pic I upload

[zgbilltalent]

What shuld I give it to you ？

[zgbilltalent]

https://github.com/faithfracture/Apple-Boost-BuildScript this is the shell which I used to compile
version 1.77.0

[Lastique]

From the backtrace it looks like the directory iterator is located at an invalid location (or this is an invalid pointer, which is more likely). This looks like either a compiler bug (miscompiled code) or some sort of ABI mismatch between your code and Boost compiled libraries.

In your Boost build scripts you're defining BOOST_AC_USE_PTHREADS and BOOST_SP_USE_PTHREADS here. Are you defining the same macros when you're compiling your own code? These macros affect ABI of atomic reference counters in smart pointers, including intrusive_ptr that is used in directory_iterator internally, and must be defined (or not defined) consistently when building Boost and your code.

Note that you should not need to define these macros. Boost.SmartPtr should detect an use a better implementation for atomic reference counters.

[zgbilltalent]

faithfracture/Apple-Boost-BuildScript#50 I think this is the problem

[Lastique]

Closing as a duplicate of #147 then.